96
edits
GitHub/GHE SAML User FAQ: Difference between revisions
Jump to navigation
Jump to search
→SAMLing to the org: SAML timeouts
Cknowles-moz (talk | contribs) (→Troubleshooting: Adding information around vscode extensions and SAML) |
Cknowles-moz (talk | contribs) (→SAMLing to the org: SAML timeouts) |
||
| Line 65: | Line 65: | ||
If this works, you've SAML'd - though there might be more steps you'll need to take if you're using keys, or tokens, or other integrations, read on. | If this works, you've SAML'd - though there might be more steps you'll need to take if you're using keys, or tokens, or other integrations, read on. | ||
=== SAML Timeouts (or, "Why do I have to click a button EVERY day?!") === | |||
SAML sessions to GitHub timeout after 24 hours per GitHub's defaults. And unfortunately Auth0 and GitHub speak sufficiently different dialects of SAML that the timeouts that we use with other providers aren't working, and multiple support tickets with GitHub and Auth0 have yet to resolve the issue. | |||
If this is horrific imposition for you, we may be able to help with strategies to lessen or avoid the concern - please reach out to our bug/email channels and we're happy to discuss. | |||
== Alright, I've SAML'd what now? == | == Alright, I've SAML'd what now? == | ||