Bug 1460963

Summary: "Last login time" time stamp doesn't update, when Satellite 6 is configured with gssproxy
Product: Red Hat Satellite Reporter: Nagoor Shaik <nshaik>
Component: AuthenticationAssignee: Marek Hulan <mhulan>
Status: CLOSED ERRATA QA Contact: Kedar Bidarkar <kbidarka>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.2.9CC: bbuckingham, kbidarka, mhulan, pa.van.der.sar, sthirugn, zhunting
Target Milestone: UnspecifiedKeywords: Triaged, UserExperience
Target Release: Unused   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-21 16:54:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
first time stamp after login
none
Second timestamp after logout and login again none

Description Nagoor Shaik 2017-06-13 09:15:53 UTC 
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.
Comment 2 Marek Hulan 2017-08-14 15:07:10 UTC 
Created redmine issue http://projects.theforeman.org/issues/20589 from this bug
Comment 3 Satellite Program 2017-09-07 10:07:34 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20589 has been resolved.
Comment 5 Kedar Bidarkar 2018-02-02 10:53:49 UTC 
"Last login time" timestamp now does get updated, when Satellite6 is configured with gssproxy.


VERIFIED with Sat6.3.0-snap34.0
Comment 6 Kedar Bidarkar 2018-02-02 10:55:07 UTC 
Created attachment 1390086 [details]
first time stamp after login
Comment 7 Kedar Bidarkar 2018-02-02 10:55:54 UTC 
Created attachment 1390087 [details]
Second timestamp after logout and login again
Comment 8 Satellite Program 2018-02-21 16:54:17 UTC 
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