OAuth 2.0 and ServiceNow - does it work?

[Mykenna Cepek]

I'm collaborating with one of our ServiceNow engineers to switch our ServiceNow/Jira integration from basic authentication to an OAuth 2.0 Atlassian Service Account credential.

I've read all the docs on the Atlassian side, which focus only on how to create the credential (trivial). I have provided the Client ID, Client Secret, CloudID, and these URLs:

• Token URL: https://auth.atlassian.com/oauth/token
• Authorization URL: https://auth.atlassian.com/authorize
• Connection URL: https://api.atlassian.com/ex/jira/<cloudId>
• Refresh Token URL: same as Token URL

My counterpart with ServiceNow keep reporting they are not able to authenticate with Jira. Based on what I see, the ServiceNow documentation was written before Atlassian introduced Service Accounts, which makes it difficult for me to help them connect their dots.

My questions are simple:  Has anyone successfully used Atlassian's OAuth 2.0 Service Account credentials with ServiceNow? At this point, I doubt it. But if so:  What was the trick to getting it to work?

[Matteo Vecchiato]

Hi @Mykenna Cepek ,

I suggest first to test the API call with a client like Postman or others, in order to define the correct API call and discard errors from servicenow side.

Hope it helps 

[Mykenna Cepek]

Tests like this help when there are no connectivity concerns, and the focus is correct credential data or correctly formatted web requests (proper endpoint, http headers, etc). They're a fine first step, but far from definitive.

Such a test will come from a user's computer or laptop to the endpoint, rather than from the actual target system. I might be able to hit Jira Cloud fine, but network configuration (e.g. IP allowlists) might prevent ServiceNow from doing so.

Past experience suggests to me that we are more likely experiencing some ServiceNow configuration or networking/connectivity challenge instead. The former makes me genuinely wonder if anyone has ever gotten this to work. Thus my OP.

I no longer am working on this, so please feel free to abandon this question/thread. I appreciate all the input.

[Ignacio Vera]

Are you referring to the ones you created in the Admin Hub? If so, which scope did you select for that service account? That could be causing the issue.

[Mykenna Cepek]

Yes, these were the scopes associated with an OAuth 2.0 Service Account credential. I created it as a site admin.

The scopes for the credential were selected to exactly match what the ServiceNow documentation says it needs here.

Some of those scopes concern me (delete sprints? really??) but we're testing in a sandbox to try to get anything to work. Then we'll experiment with fewer scopes.

[Ignacio Vera]

OMG, what are the odds? I have to do the same now

Did you made it work??

[Ignacio Vera]

@Mykenna Cepek 

[Mykenna Cepek]

Not yet. As noted in my response to another answer here, someone else here is working on this. The support ticket we have open with Atlassian is proceeding very slowly. No progress as of yet.