[katello-devel] password reset - branch merged to master

[Brad Buckingham]

On 11/16/2011 10:32 AM, Jeff Weiss wrote:
> On Wed, 2011-11-16 at 07:28 -0700, Jason Rist wrote:
>> On 11/15/2011 07:29 AM, Brad Buckingham wrote:
>>> Team,
>>>
>>> I've merged the password reset branch to master.
>>>
>>> With this merge, if a user forgets either their login or password, they
>>> now have the ability to request their logins and well as reset their
>>> password.  The following is a basic flow:
>>>
>>>      1. go to the Katello login page
>>>      2. click 'Forgotten username or password?'
>>>
>>>      - if user forgot their username, they can enter their email address
>>> and the username will be sent to them in email
>>>
>>>      - if the user forgot their password, they can enter their login and
>>> email address  and an email will be sent to them with details on
>>> resetting their password.  Note: Password reset requests are based on
>>> tokens that get generated by the server.  By default, these tokens will
>>> expire after 2 hours; however, this is configurable in the
>>> /etc/katello/katello.yml via the 'password_reset_expiration' field.
>>>
>>> With the above come a few changes to be aware of:
>>>
>>> 1. Email addresses are now a required attribute for users.  To support
>>> this:
>>>      - User UI create&  edit have been updated
>>>      - User CLI has been updated
>>>      - Installer (katello-configure) has been updated to include
>>> providing email for the 'first user'
>>>
>>> 2. The server needs to be configured with sendmail, which is current
>>> default on the OS
>>>
>>> 3. The katello configuration needs to know details about the server
>>> FQDN, port and protocol.  To support this:
>>>
>>>      - If using the installer (katello-configure), this is handled by the
>>> installer.  The following is an example of what is added to
>>> /etc/katello/katello.yml for a typical production configuration:
>>>
>>>              host: some.katelloserver.com
>>>              use_ssl: true
>>>              port:
>>>
>>>              (Note: the port is left empty in this case, since we are
>>> using the default SSL port)
>>>              (Note: use_ssl is now used to identify the protocol to be
>>> used (e.g. https))
>>>
>>>      - Note: as a developer, you will need to add similar attributes to
>>> your /etc/katello/katello.yml.  For a typical developer configuration,
>>> this might look like:
>>>
>>>              host: some.devserver.com
>>>              use_ssl: false
>>>              port: 3000
>>>
>>> With this merge, developers will also need to run 'rake db:migrate' to
>>> update the schema for user email.
>>>
>>> thanks,
>>> Brad
>>>
>>> _______________________________________________
>>> katello-devel mailing list
>>> katello-devel at redhat.com
>>> https://www.redhat.com/mailman/listinfo/katello-devel
>> Will this work with Postfix?  RHEL6 defaults to Postfix.
>>
>> -J
>>
> FWIW, I installed last night on vanilla RHEL 6.1, it "just worked".
>
> -jeff
>
> _______________________________________________
> katello-devel mailing list
> katello-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/katello-devel
Jeff,

Thanks for the update.

Actually, it should.  The use of 'sendmail' was probably improper.  
RAILS refers to 'sendmail'; however, it is actually handling the mailing 
for the app.  The real requirement is that we have mail installed and 
running on the system.  I've not tried it across all possible mail 
combinations, though.

cheers,
Brad