Project

General

Profile

Actions

Bug #20589

closed

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

Added by Marek Hulán over 7 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Authentication
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1460963

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.


Files

after-patch.png View after-patch.png 142 KB Nagoor Shaik, 08/14/2017 11:18 AM
before-patch.png View before-patch.png 132 KB Nagoor Shaik, 08/14/2017 11:18 AM
Actions

Also available in: Atom PDF