Jira Spoke - Basic Auth is deprecated

[rickburke]

I am thinking this was a super simple question to answer, but it seems I can't find the answer no matter how detailed I make my search.

We have installed the Jira Spoke in our DEV instance and looked at many articles to configure the spoke.  Most of it was very straight forward as I would expect Spoke Setup to be, however it appears that Jira has deprecated the Basic Auth at least a year ago, and some cases it looks like 2 years ago. 

Has ServiceNow not updated their Spoke Setup?

We are on San Diego and when I try and create an Update Issue through Flow Designer, we get an error saying that Basic Auth has been deprecated and points us to an Atlassian article about API's. We are using an e-mail setup on Jira that has Admin access to the project and the password is indeed the API key that was generated from Jira (2 different times), but we still get that error message.  

I went ahead and tried with creating a credential that was simply an API key (instead of basic auth) and now we don't get that error, but now we get "Issue does not exist or you don't have access".  We have checked to make sure the API group/role in the permission scheme has the proper access to the project, but still nothing.  If I follow the rest url with the original user logged into the browser, we see the data just fine.

I'm just curious if others have ran across the Deprecation error and what they did to fix it.

[Allen Andreas]

Hi,

Have you followed documentation such as: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0792632

Using the API key as the password, as indicated.

You'd want to ensure it's correctly established from Atlassian side of things.

This would be all that's needed, otherwise, it's a user permission issue on Atlassian side and not ServiceNow.

Please mark reply as Helpful/Correct, if applicable. Thanks!

[rickburke]

Yes, those are the exact steps that we took to begin with and that is when we are getting the error that Basic Auth has been deprecated. We then created an API Key Credential only on SNOW as this is one of the options when you create credentials and this is when we get the error issue does not exist or you don't have access to it.  There is not a field on the API key form for username, so I tried it without the user name and we get the same error.  We also added the username field to the API Key form and we still get the same error. If we navigate to the Rest API URL while not logged into Jira, we get the same error from a broswer, but if we navigate to that same URL while the user is logged in to Jira, we get the XML (response) expected.

[rickburke · Accepted solution]

This is solved now.  I am not the Jira Admin so I can't say for sure where this is, but apparently there are 2 places to build API keys.  As I understand it, there is an API key for the entire site that gets created in the Admin settings, however the API that needs to be created for this spoke to work should be under the project itself.  That was the case and once the API key was created in that location, we were able to use the Basic Auth that is provided by the original spoke.  I am guessing because it sees an API key instead of a simple password it knows that it is an API key and not just simple basic auth with username and password. 

[asifnoor]

Hello @rickburke 

Where exactly did you create the aPI key in the project? I do not see any option in Jira to do that.