You want to use the gcloud command-line tool to authenticate using a third-party single sign-on (SSO) SAML identity provider. Which options are necessary to ensure that authentication is supported…

Question

Options

• ASSO SAML as a third-party IdP
• BIdentity Platform
• COpenID Connect
• DIdentity-Aware Proxy
• ECloud Identity

• A
  83% (33)
• B
  5% (2)
• D
  3% (1)
• E
  10% (4)

Explanation

To authenticate gcloud CLI through a third-party SAML SSO identity provider, two things must be in place: (A) the third-party IdP must be configured to federate via SAML - this is the identity source - and (C) OpenID Connect (OIDC) must be supported, because gcloud uses browser-based OAuth 2.0 / OIDC flows to exchange the SAML assertion for Google-compatible tokens via Workload Identity Federation or Cloud Identity external IdP configuration. Identity Platform (B) is a customer-facing auth product, not a mechanism for authenticating gcloud CLI users. Identity-Aware Proxy (D) controls access to applications, not CLI authentication. Cloud Identity (E) is Google's own identity directory and would not be a 'third-party' IdP in this context.

No community discussion yet for this question.