I am trying to move away from personal user API tokens and onto Service Account tokens for automated tasks we run outside of JIRA. The scopes I see in the Service Account section all seem to be for the Jira Cloud Platform APIs:
Is it possible to scope to the Jira Service Management Cloud APIs with a Service Account?
Hi @Cody ,
As far as I know, the Jira scopes are largely the same as for JSM. But the JSM scopes can be found here: https://developer.atlassian.com/cloud/jira/service-desk/scopes-for-oauth-2-3LO-and-forge-apps/
Have a nice day.
Rik
@Rik de Valk I think my confusion is that for Jira scopes I can easily add the needed 'classic' scopes to a Service Account credentials since 'Jira' is one of the app options available when you create the credentials.
However, JSM is not an option when I am trying to configure the Service Account Credential.
Its a bit difficult for me to tell from the documentation because both the Jira and JSM documentation appear to say that OAuth 2.0 grants should be used for 3LO apps created in the Developer Console but for the Jira scopes I CAN use the Service Account without creating a Developer Console app.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Cody
Welcome to the community.
You can't use the JSM API endpoints with a scoped token. the API endpoints in the JSM API mentioned by @Rik de Valk don't have granular scopes defined.
So these can't be used based on a granular scope for now, I hope this will change.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.