GitHub/GHE SAML User FAQ: Difference between revisions

Jump to navigation Jump to search
→‎Alright, I've SAML'd what now?: Adding lines around OAuth
(→‎SAMLing to the org: SAML timeouts)
(→‎Alright, I've SAML'd what now?: Adding lines around OAuth)
Line 93: Line 93:
** When you hit the "Authorize" button, you'll do the Auth0/2FA dance  
** When you hit the "Authorize" button, you'll do the Auth0/2FA dance  
* Once you've authorized all the organizations you want to, you'll be asked to "Authorize GitHub" - do this, and you should be back to working.
* Once you've authorized all the organizations you want to, you'll be asked to "Authorize GitHub" - do this, and you should be back to working.
=== Reset OAuth Tokens ===
If any OAuth'd apps stop working, you may need to reset their tokens.  To date we've seen this with GitHub plugins for VS Code, though others do it as well.
Unlike SSH/PAT, OAuth doesn't currently have a way to update the token with new authentications. 
* First, try logging out/back in for the OAuth'd thing. 
* Second, try revoking the token using the directions [https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations#reviewing-your-authorized-oauth-apps here]
* After revoking, redo the setup of the affected system again to regenerate the token.


== Troubleshooting ==
== Troubleshooting ==
96

edits

Navigation menu