{{ message }}
GitHub SSO Re-Authentication Timeout #50334
Unanswered
rnhurt
asked this question in
Enterprise
Replies: 1 comment 6 replies
|
The default timeout for GitHub SSO authentication tokens is six hours. This means that after six hours of inactivity, you will be prompted to re-authenticate. However, GitHub does provide a way to adjust the session timeout. This can be done by the organization owner or administrator in the organization's SAML settings. Here's how:
Keep in mind that a longer session duration can increase the risk of unauthorized access if your device is lost or stolen, so it's important to balance convenience with security when adjusting this setting. |
6 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment


Uh oh!
There was an error while loading. Please reload this page.
Select Topic Area
Question
Body
We recently started using SSO to authenticate to GitHub and everything seems to be working fine. The one thing that is bothering me is the re-authentication timeout. I'm not sure how long the "session" is supposed to last but it feels like I'm re-authenticating multiple times per day.
It's not a huge problem, but it is a bit jarring when the browser refreshes while your trying to update an Issue or modify your Project. Most other systems don't really re-auth that often so I'm not really sure why GitHub is so needy. Hell, before we moved to SSO I didn't re-auth at all unless I had to do something "risky" (create a PAT, delete a repo, etc.) Why does SSO require so much re-authentication?
Questions
All reactions