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
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.
Timestamp for External users created via GSSProxy authentication doesn't get updated.
Timestamp should be updated.
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.