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

ServiceNow and Jira Integration

Community Alums
Not applicable

I am integrating ServiceNow and Jira using OAuth 2.0 authentication. I have successfully configured the integration and granted the necessary permissions in Jira, but I am still getting a 401 - Client must be authenticated to access this resource error when I try to access Jira resources from ServiceNow or Postman. Can anyone help me troubleshoot this issue?tempsnip.png

6 REPLIES 6

Vijay Balotia1
Tera Guru

Hi Gowtham,

 

For Jira integration generally it recommended to provide Admin level access, looking into the error its seems you haven't provided the required access.

If you want to give full access the you have provide Admin level access or if you want to restrict the access then make sure you provide access to at least one jira resource or project.

 

Apart from this ServiceNow support Jira Integration OOTB for that your can use OOTB Jira Spoke  or Atlassian Jira Integration for Agile Development spoke. 

For more detail you can check below:

KB Article: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0792632

Product Document : https://docs.servicenow.com/en-US/bundle/vancouver-it-business-management/page/product/agile-jira-in...

 

Thanks,

Vijay Balotia

Please mark the appropriate response as correct answer and helpful, This may help other community users to follow correct solution.
Thanks
Vijay Balotia

Mathieu Lepoutr
Mega Guru

Hi

 

If you're getting a "401 - Client must be authenticated to access this resource" error while trying to integrate ServiceNow and Jira using OAuth 2.0, it suggests an authentication problem. Ensure that the OAuth 2.0 configuration is correctly set up in both Jira and ServiceNow. Make sure the client_id and client_secret from Jira are correctly configured in ServiceNow (or in Postman for testing purposes) and lastely check the validity of the access token. Tokens can expire, and when they do, you'll get a 401 error.

 

 

For use-cases like this I always suggest using Exalate, a decentralized integration solution. It provides robust syncronization capabilities and you can granuarly decided what you want to send to the other side and how you want to apply receiving information. I have been using it for quite a while and it instantly jumped in my thoughts reading this post. Hope to have helped you

ParthMittal
Tera Contributor

This issue actually happens after 1 hour of generating oauth token. Issues is with refreshing the token. I am having the same issue and am investigating it further. 

Just wondering @Community Alums  did you find a solution?

Were you able to resolve this? We are encountering the same issue.