JIRA API Authentication - Cookie - No JSESSIONID but cloud.session.token

Leo_M

I got this as response on trying to authenticate using rest/auth/1/session 

{"session":{"name":"cloud.session.token","value":"eyJraWQiOiJzZXNzaW9uLXN

Can i use this as JSESSIONID  ?

Another case is 

I am able to connect using Basic authentication after that am stuck. After login if there is a redirect ,   do i have to authenticate again on the new page ? So if i have multiple pages do i have to authenticate each time if i am using Basic Auth ?

 

Dario B

Hi Leo,

The documentation needs to be updated as mentioned in:

• https://jira.atlassian.com/browse/JRACLOUD-62515
•  https://jira.atlassian.com/browse/JRACLOUD-63933

In  order to make it working you just store all the cookie information in a file and use that to authenticate. E.g.:

1) Store the cookie in a cookie jar: 

curl -c cookie.txt -H "Content-Type: application/json" -d '{"username":"XXXXXXXXX", "password":"XXXXXXXXX" }' -X POST https://INSTANCE/rest/auth/1/session

OR

curl --cookie-jar cookie.txt -H "Content-Type: application/json" -d '{"username":"XXXXXXXXX", "password":"XXXXXXXXX" }' -X POST https://INSTANCE/rest/auth/1/session 

 

2) You can then use that to authenticate the successive REST calls:

curl -b cookie.txt --header "X-Atlassian-Token: no-check" -H "Content-Type: application/json" -X GET https://INSTANCE/rest/........

OR

curl --cookie cookie.txt --header "X-Atlassian-Token: no-check" -H "Content-Type: application/json" -X GET https://INSTANCE/rest/........ 

 

Cheers,
Dario