Oauth token endpoint giving 404 error

The endpoint https://auth.atlassian.com/oauth/token is currently giving a 404 error with message “Not found.”

This is the endpoint directly from the documentation here: https://developer.atlassian.com/cloud/jira/platform/oauth-2-3lo-apps/#faq1

My code had been working fine without issue for months and now my login flow doesn’t work and it seems to be because of this 404. Is this a known issue that is affecting other people?

@Luke welcome to the Atlassian developer community.

I just ran through the flow with a new authorization code and I get an HTTP status 200 with a valid access token response. Your 404 sure is puzzling and I can’t think of any recent 3LO changes recently. Is there anything interest in the response headers?

I solved the issue I was having (it was an unrelated cURL firewall issue), it seems the 404 was a red herring, but confusing nonetheless.

If you visit https://auth.atlassian.com/oauth/token (without any query parameters) it returns a 404 status code and the message “Not Found.” This doesn’t seem like correct behaviour to me and would perhaps confuse others in the future.

1 Like