An enterprise wants to use OpenID Connect (OIDC) for enterprise SSO instead of SAML. What is a primary administrative characteristic of OIDC enterprise SSO on GitHub?
Select an answer to reveal the explanation.
Short Explanation and Infographic
OIDC SSO is another way to federate enterprise login — modern OAuth/OIDC flows with your IdP instead of classic SAML XML assertions. It is still about people signing into GitHub under enterprise policy, not only machine OIDC for Actions cloud roles. You still manage org membership, apps, and authorization separately from the authentication protocol choice.
Full explanation below image
Full Explanation
The correct answer is that OIDC enterprise SSO federates interactive enterprise authentication via OIDC with an identity provider rather than relying on SAML assertions for that enterprise login path. Enterprises choose OIDC or SAML based on IdP capabilities and security standards; both are authentication federation options at enterprise scope when supported for the account type. Option B confuses enterprise user SSO with GitHub Actions OIDC for cloud provider roles. Option C is false; GitHub Apps remain independent. Option D is false; authentication method does not eliminate organization membership models. Admins should pilot claims mapping, session behavior, and break-glass access before forcing the enterprise to OIDC-only login.