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:
If Access Token Lifespan is set to 5 mins then the user is getting sign out instead after idle SSO timeout 

Version-Release number of selected component (if applicable):
Satellite 6.7 Snap 10

How reproducible:
Always 

Steps to Reproduce:
1. Setup the Satellite with RHSSO instance and Keep Access Token Lifespan = 5 min
2. Keep SSO Session Idle = 30 mins 
3. Setup the Smart Card with firefox browser and login using a smart card in Satellite
4. Go Idle for 5 mins 
5. User is getting Signout from the application after 5 mins instead of 30 mins of idle session

Actual results:
User is getting Signout 

Expected results:
User should not get Signout 

Additional info:
This seems to be an issue with a refresh token if JWT token got expired, need to renew with the use of Refresh Token.

*** Bug 1798488 has been marked as a duplicate of this bug. ***

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

Now Access Token Lifespan from RHSSO is no more use after integrating Satellite. The Satellite has the setting for the 'Idle timeout' which manages the session idle timeout

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 (Important: Satellite 6.8 release), 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-2020:4366