The Zurich release has arrived! Interested in new features and functionalities? Click here for more

Jira/SN integration Refresh Token

StephanieR05634
Tera Contributor

We are struggling with the refresh token for our Jira/SN integration. Here is the summary of notes from a recent discussion.

 

  • We've discussed how you are able to create the connection and it works the first time you send a request, but after 30-60 minutes, the process starts to fail and it's necessary to re-authenticate from scratch for the connection to work

  • You've confirmed that you notice the problem "there seems to be a problem with your identity provider" and "error":"unauthorized_client","error_description":"refresh_token is invalid" after the first connection succeeds

  • I've shared that the refresh tokens expire immediately upon use, so each time a refresh token is used, a new access token and a new refresh token are issued

  • You've shared that it seems that the access token is getting expired in around 30 minutes

 

For SN token request.png

 

How do we get around this error? I have approached it from both the SN and Atlassian side and we still haven't been able to properly complete the connection.

1 REPLY 1

Bhuvan
Kilo Patron

@StephanieR05634 

 

Can you share more details how you have setup OAuth ?

 

Are you using ServiceNow as OAuth provider or JIRA as the OAuth provider ? From your screenshots it looks like you have configured 'Connect to an OAuth Provider Outbound' or 'Connect to a third party OAuth Provider - Outbound'.

 

ServiceNow OAuth registry makes the process of fetching access tokens and refresh tokens automatically. If you have configured the OAuth registry correctly, it should not result in error. Can you share the OAuth configuration and explain in detail the process setup and what is not working ?

 

If this helped to answer your query, please mark it helpful & accept the solution. 

 

Thanks,

Bhuvan