topic RE: JIRA API Authentication 401 in Product Forum

JIRA API Authentication 401

BenAnderson — Mon, 23 Jan 2023 19:30:00 GMT

Hi,

I recently started setting up the JIRA API skill, and have followed the User Guide that comes with it and gone through each step. I have set up the API in the 'Web API Services' section of the BP system settings. I have set up a credential and obtained an API Key from Atlassian. However whenever I try to run it in a process, I keep receiving an error message, "HTTP Status Code:401; Basic authentication with passwords is deprecated".

I have looked in the BP communities, and read through the Atlassian documentation, although I can't seem to find any information on where I am going wrong. Any help on resolving this would be greatly appreciated. The credentials I have work fine when logging in manually.
Please see below for some screenshots of the error message, and API configuration.

Many thanks for any help,
Ben

Many thanks,
Ben

------------------------------
Benjamin Anderson,
Senior Consultant,
UK
------------------------------

RE: JIRA API Authentication 401

ewilson — Mon, 23 Jan 2023 20:25:00 GMT

Hello @Benjamin Anderson,

Based on the error response, it seems that the authentication mechanism implemented in the Web API connector is no longer supported by JIRA's REST API. We'll need to spend a little time investigating this. Stay tuned.

Cheers,

------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------

RE: JIRA API Authentication 401

ewilson — Mon, 23 Jan 2023 20:47:00 GMT

@Benjamin Anderson,

When you say the credentials you have work for manually logging in, you're referring to username/password credentials, correct? Do you have an API key by chance? If you review the main JIRA API connector asset's user guide you'll see that it discusses the need for an API key to be used in place of passwords.

The deprecation notice, viewable at the URL included in the error message you received, discusses the same thing.

Cheers,

------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------

RE: JIRA API Authentication 401

BenAnderson — Mon, 23 Jan 2023 21:16:00 GMT

Hi @ewilson,
Many thanks for reply.
That's correct. Yeah, I can login to the website with normal credentials (UN and PW). Whenever I use the skill in a BP process I'm using an API key which I generated from the Atlassian website.
Would I be correct in saying that the above screenshots show that the skill/api has been configured correctly in my environment?
Many thanks,
Ben

------------------------------
Benjamin Anderson,
Senior Consultant,
UK
------------------------------

RE: JIRA API Authentication 401

mkumar407 — Tue, 24 Jan 2023 07:18:00 GMT

Hi @Benjamin Anderson,

The Jira REST API requires a BASE64 encoded header that is built from a string of the form:
"useremail:api_token"
- Example: user@example.com:api_token_string

To achieve this within Blue Prism, please find the Base64Encoder Utility on the Digital Exchange here:
https://digitalexchange.blueprism.com/dx/entry/3439/solution/base64encoder-2

You can also find other ways to produce the Base64 on the Jira documentation here:
https://developer.atlassian.com/cloud/jira/platform/basic-auth-for-rest-apis/#get-an-api-token

Hope this helps!

------------------------------
Manish Kumar
------------------------------

RE: JIRA API Authentication 401

BenAnderson — Tue, 24 Jan 2023 08:25:00 GMT

Hi @Manish Kumar,

Many thanks for the reply.

Yeah, I use the Base64 to encode the key as "myemail:apiKey".

I then passed this encoded text into the "Basic Auth" input as: "Basic " & [EncodedText]
Please see below:

Many thanks for your help,
Ben

------------------------------
Benjamin Anderson,
Senior Consultant,
UK
------------------------------

RE: JIRA API Authentication 401

ewilson — Tue, 24 Jan 2023 14:57:00 GMT

@Benjamin Anderson,

So you're passing "Basic " & [EncodedText] into the WebAPI for the Basic Auth input parameter. All you should be passing in is [EncodedText]. The WebAPI definition already accounts for the "Basic " portion of the header value.

Cheers,

------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------

RE: JIRA API Authentication 401

BenAnderson — Tue, 24 Jan 2023 16:56:00 GMT

Thanks @ewilson,

I made the change you suggested but unfortunately, I'm getting a status code of 401 now. "HTTP Response Content: Basic authentication with passwords is deprecated". (Which is odd as I'm not using a password - just the API key).

I generated the API key a few days ago following the user guide, so it is valid.

Many thanks,
Ben

------------------------------
Benjamin Anderson,
Senior Consultant,
UK
------------------------------

RE: JIRA API Authentication 401

BenAnderson — Fri, 27 Jan 2023 10:06:00 GMT

Hi @ewilson,

I was reading through the user guide again for the JIRA api, and noticed the below comment.

Does this then mean that I have to manually log in to JIRA through the browser in order to use the API?

Many thanks,
Ben

------------------------------
Benjamin Anderson,
Senior Consultant,
UK
------------------------------

RE: JIRA API Authentication 401

ewilson — Fri, 27 Jan 2023 14:42:00 GMT

Hello @Benjamin Anderson,

No, I don't think that's the case. It would defeat the purpose of having an API. I'm checking with the developer of the connector to get their input though.

Cheers,

------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------

RE: JIRA API Authentication 401

ewilson — Fri, 27 Jan 2023 15:13:00 GMT

@Benjamin Anderson,

I just realized the original developer of this connector is no longer with Blue Prism. I've put together a quick test retrieving the details of a JIRA issue including the creation of an API key (I am not logged into JIRA via the browser BTW). My test is running as expected and I'm able to retrieve the details of the specific issue. Here are a few screenshots of my little test process:

I've also tested it with getFeaturesForProject action, and that works as expected for me. So it seems to be something with your environment. Can you try creating a new API key under your account?

Cheers,

------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------

RE: JIRA API Authentication 401

BenAnderson — Mon, 30 Jan 2023 20:45:00 GMT

Hi @ewilson,

Thank you very much for the above screenshots. I managed to get an HTTP status code of 200 indicating that the authorization is working. However, the Response Content looks not so much like features or issues within the JIRA project, but more like the HTML source code for the web-page. Please see below:

I'll keep testing, and see if I can figure it out.

Many thanks,
Ben

------------------------------
Benjamin Anderson,
Senior Consultant,
UK
------------------------------

RE: JIRA API Authentication 401

ewilson — Mon, 30 Jan 2023 22:54:00 GMT

@Benjamin Anderson,

That's definitely not the response content you should be seeing. 🤔 I'll dig a bit deeper on our side too, and see if there's anything else I can turn up.

Cheers,

------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------