After SAML SSO is enforced for an organization, what must a member typically do before using a personal access token or SSH key against organization resources that require SSO authorization?
Select an answer to reveal the explanation.
Short Explanation and Infographic
With SSO enforced, PATs and SSH keys need to be SSO-authorized for that org. Turning off 2FA or deleting personal repos is not the fix.
Full explanation below image
Full Explanation
When an organization enforces SAML SSO, members must authenticate through the IdP and authorize eligible credentials (such as PATs or SSH keys) for SSO use with that organization. Until authorization succeeds, API and Git operations against protected organization resources can fail even if the credential works elsewhere. Disabling 2FA, converting the org to a user namespace, or deleting personal repositories does not satisfy SSO credential linking. Administrators should publish runbooks for first-time SSO, credential authorization screenshots, and break-glass owner accounts. Automated systems should prefer GitHub Apps or carefully managed machine identities with documented SSO authorization steps.