OpenID support

Jan Milata

Hello,

We would like to ask whether Atlassian plans to introduce native support for OpenID Connect (OIDC) for single sign-on and identity provider integration in Atlassian Cloud.

At the moment, OIDC is not supported for this purpose, and organizations need to use SAML 2.0. One of our customers uses an identity platform where OIDC is the preferred integration standard, so the current limitation may significantly affect the proposed target architecture.

Could you please clarify:

• whether native OIDC support is included in the Atlassian roadmap,
• whether there is any expected or tentative delivery timeframe,
• and whether Atlassian recommends any supported alternative for customers whose identity provider primarily relies on OIDC?

Thank you for any information you can share.

Best regards,
Jan

Gabriela - LeanZero

Hi @Jan Milata, your read is correct. Atlassian Guard only supports SAML 2.0 for account-level SSO, and OIDC isn't available for that in Cloud today.

Native OIDC is tracked as a feature request, ACCESS-625, currently at "Gathering Interest". Atlassian hasn't committed a delivery date and I wouldn't read a timeframe into it; voting and watching that ticket is where you'll catch any movement. (The JSM portal side was split into a separate request, JSDCLOUD-14859.)

Atlassian's recommended alternative is to fall back to SAML 2.0. Most platforms that prefer OIDC (Entra, Okta, Ping, Keycloak, Auth0) also expose a SAML 2.0 app, so you configure that against Guard and handle provisioning with SCIM. If your customer's IdP genuinely can't do SAML, a Marketplace SSO app like miniOrange can broker OIDC into Cloud.

Best, Gabriela