Jira OAuth 2.0

[AutomationUIUser]

We are currently implementing OAuth 2.0 Authorization Code flow for authentication with Jira Cloud.

As part of our integration, users are redirected to the Atlassian authorization page, where they sign in and approve access. After approval, an authorization code is generated and returned to our application, which we then exchange for an access token.

We would like to clarify user support for this flow:

Can Jira Service Management users (portal/customers) use OAuth 2.0 Authorization Code flow for authentication and authorization in Jira Cloud? Or is this OAuth 2.0 flow supported only for Jira administrators and licensed Jira users?

We need to confirm whether non-admin service users are eligible to complete the full OAuth 2.0 authorization flow (login → consent → authorization code → token exchange) in our integration setup.

[Ajay _view26_]

Hi @AutomationUIUser 

No, JSM portal-only customers (unlicensed/customer accounts) cannot complete the OAuth 2.0 Authorization Code flow.

The OAuth 2.0 (3LO) flow is designed for licensed Jira/JSM users — agents, admins, and users with product access. JSM portal customers (sometimes called "customer accounts") don't hold a product license — they access the portal via a customer account that lives outside the licensed user pool. When they try to go through the OAuth consent screen, they either won't see any accessible resources to authorize, or the token exchange will fail because the resulting token has no scopes tied to a licensed product.