Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
"Last login time" time stamp doesn't update, when Satellite 6 is configured with gssproxy

Version-Release number of selected component (if applicable):
Red Hat Satellite 6.2.9

How reproducible:
100%

Steps to Reproduce:
1. Install Red Hat Satellite 6.2.9, and configure AD authentication using https://access.redhat.com/documentation/en-us/red_hat_satellite/6.2/html/server_administration_guide/sect-red_hat_satellite-server_administration_guide-configuring_external_authentication-using_active_directory#sect-Red_Hat_Satellite-Server_Administration_Guide-AD_direct
2. Try logging with AD user, which would create new User entry with the timestamp.
3. Log out and then try to login again after few minutes, however the timestamp doesn't get update, still shows the timestamp when the user is first created.

Actual results:
Timestamp for External users created via GSSProxy authentication doesn't get updated.

Expected results:
Timestamp should be updated.

Additional info:
Note: When LDAP Authentication is configured via WebUI using https://access.redhat.com/solutions/1498773, timestamp updates correctly.

Created redmine issue http://projects.theforeman.org/issues/20589 from this bug

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20589 has been resolved.

"Last login time" timestamp now does get updated, when Satellite6 is configured with gssproxy.


VERIFIED with Sat6.3.0-snap34.0

Created attachment 1390086 [details]
first time stamp after login

Created attachment 1390087 [details]
Second timestamp after logout and login again

Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.
> 
> For information on the advisory, and where to find the updated files, follow the link below.
> 
> If the solution does not work for you, open a new bug report.
> 
> https://access.redhat.com/errata/RHSA-2018:0336