-
Bug
-
Resolution: Fixed
-
Highest
-
None
-
127
-
Severity 2 - Major
-
184
-
Summary
REST API calls that uses email in basic authentication to the JIRA Cloud endpoint rest/auth/1/session fails with 401 error on instances that have been upgraded to Atlassian account.
Steps to Reproduce
1. Make sure the user can login fine to JIRA cloud and can make REST requests to other endpoints.
2. Access rest/auth/1/session via a rest api call using the same basic authentication with email/password
Expected Results
The rest api call should authenticate and the session information will be retrieved.
Actual Results
The rest api call will fail with 401 error.
<html>
<head>
<title>Unauthorized (401)</title>
<!--[if IE]><![endif]-->
<script type="text/javascript" >
var contextPath = '';
var DeferScripts = { deferState: 'disabled' };
</script>
<script>
Workaround:
You can call this resource using your JIRA username and Atlassian account password. Like this:
POST https://your-domain.atlassian.net/rest/auth/1/session
{ "username" : "admin",
"password" : "$ATLASSIAN_ACCOUNT_PASSWORD"}
If you do not know if your instance has been upgraded to Atlassian account or you don't know your Atlassian account password, you can verify this and reset your password from your JIRA Cloud profile page (https://your-domain.atlassian.net/secure/ViewProfile.jspa)
Other related problems
Several customers are having problems with basic authentication for other endpoints. There is currently no confirmed bug on these endpoints, however some potential fixes have been listed on this comment
- relates to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
ACEJS-95 Loading...
-
-
- Followed up by
-
- is related to
-
- mentioned in
-
-
-
-
-
-