nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

HTTP Basic authentication not working anymore for jira.atlassian.com REST API

Raimonds Simano1

We were using jira.atlassian.com REST API to load some test JIRA data in our eazyBI reporting application and we were using REST API with HTTP Basic authentication (as otherwise some APIs like "user" didn't return any results) and using our jira.atlassian.com username and password. At least still in January 30 it was working.

But couple days ago I discovered that simple https://jira.atlassian.com/rest/api/latest/serverInfo with my username and password in HTTP Basic authentication header returns 403 Forbidden response.

If I try another Atlassian JIRA site, for example, https://ecosystem.atlassian.net/rest/api/latest/serverInfo with HTTP Basic authentication then it still works.

Does anyone knows what has changed in jira.atlassian.com authentication in recent weeks and why Basic authentication is not working anymore?

Kind regards,

Raimonds

Accepted answers

All comments

Nikita Marchenko

I have a problem with basic auth too. Got 401. I tried culr wget http python-request. Samples from https://developer.atlassian.com/jiradev/api-reference/jira-rest-apis/jira-rest-api-tutorials/jira-rest-api-example-basic-authentication don't work. Please help.

peterb

Are you querying jira.atlassian.com, a local dev instance of JIRA or another instance?

peterb

You have to use Atlassian ID when you are logging in to jira.atlassian.com.

I have tested these commands and they work for me.

curl \

    -i -X POST \

    -H "Content-Type: application/json"\

    https:

//<a href="http://id.atlassian.com/id/rest/login" rel="nofollow noopener noreferrer">id.atlassian.com/id/rest/login</a> \

    --data 

'{"username": "foobar@<a href="http://example.com/" rel="nofollow noopener noreferrer">example.com</a>", "password": "foobar"}'

Response:

TTP/1.1200OK

Server: nginx

Date: Mon, 03Feb 201405:57:27GMT

Content-Type: application/json

Transfer-Encoding: chunked

Connection: keep-alive

X-Frame-Options: DENY

P3P: CP=

"This is not a P3P policy! See&nbsp;<a href="http://www.atlassian.com/company/privacy" rel="nofollow noopener noreferrer">http://www.atlassian.com/company/privacy</a>&nbsp;for more info."

Set-Cookie: __ATL_TOKEN=L33TT0KEN; Version=1; Domain=.<a href="http://atlassian.com/" rel="noopener noreferrer">atlassian.com</a>; Path=/; HttpOnly

{"username":"foobar@<a href="http://example.com/" rel="nofollow noopener noreferrer">example.com</a>","xsrfToken":"xsrfToken","firstName":"Foo","lastName":"Bar"}

Use the given cookie __ATL_TOKEN for subsequent requests

curl \

    -D- -X GET \

    -H 

"Cookie:__ATL_TOKEN=L33TT0KEN; Version=1; Domain=.<a href="http://atlassian.com/" rel="noopener noreferrer">atlassian.com</a>; Path=/; HttpOnly"

\

    https://<a>jira.atlassian.com/rest/api/2/search\?jql\=project+%3D+CQ</a>

<br>

Raimonds Simano1

My question is about jira.atlassian.com. As I said I was using my Atlassian ID for HTTP Basic authentication and jira.atlassian.com REST API was working with it until end of January. But something has changed in February and now just for jira.atlassian.com site REST API with HTTP Basic authentication is returning 403 Forbidden response.

Nikita Marchenko

mirantis.jira.com and https://vetakoko.atlassian.net

Nikita Marchenko

The server at extranet.atlassian.com can't be found, because the DNS lookup failed. Can you provide another url?

Nikita Marchenko

I found solution. I use email as login instead of username in jira. Please write this to doc file.

peterb

I will copy content from that page and paste it in a new answer.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-administration