Details
-
Bug
-
Resolution: Fixed
-
High
-
12
-
Severity 2 - Major
-
3
-
Description
Summary
Internal Server Error when calling the /rest/auth/1/session REST API endpoint as described in JIRA REST API Example Cookie based Authentication
Environment
JIRA v1001.0.0-SNAPSHOT
Steps to Reproduce
- Run
curl -D- -H "Content-Type: application/json" -d '{"username":"USER_NAME", "password":"PASSWORD" }' -X POST https://INSTANCE_NAME.atlassian.net/rest/auth/1/session
Expected Results
The session information is returned in the REST response
Actual Results
Error 500 is returned instead:
HTTP/1.1 500 Internal Server Error
Server: Atlassian Proxy/0.5.38
ATL-vTM-Backend-Time: 1036
Content-Type: text/html
Strict-Transport-Security: max-age=315360000; includeSubDomains; preload
Date: Wed, 25 Jan 2017 12:46:39 GMT
ATL-vTM-Time: 1196
ETag: "5886e223-945"
Connection: close
Content-Length: 2373
ATL-vTM-Queue-Time: 0
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<meta name="description" content="">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Atlassian Cloud Notifications - Page Unavailable</title>
....
....
Notes
It doesn't matter if you use the username or the email address to authenticate. It just doesn't work.
Workaround
You can use Basic Authentication or OAuth (you can also try to use basic auth, intercept the cookie and use it to authenticate the successive requests):
