Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Periodic authentication failures with preemptive basic authentication



I'm seeing periodic failures when connecting to Jira on premise, using Crowd for authentication, via the REST API. I am using preemptive basic authentication, and I'm also passing the session cookie in subsequent responses. Because the authentication failures are periodic (the same credentials will mostly pass but occasionally fail), I'm thinking that the preemptive basic authentication might be overloading the Crowd servers and causing them to occasionally return authentication failures.

If I pass both the Authorization header and the session cookie, will it cause Crowd to re-authenticate with every request, or will the cookie be used instead? Is preemptive basic authentication not recommended for high load applications where the Crowd servers might be overloaded?


The failures that I'm seeing in Jira access logs are:

login : '<username>' tried to login but they do not have USE permission or weren't found. Deleting remember me cookie.

The user '<username>' has FAILED authentication. Failure count equals 1


The HTTP request I'm sending contains these headers:


Cookie: JSESSIONID=****; atlassian.xsrf.token=****; <crowd.token_key>=****


The HTTP response contains these headers:

Set-Cookie: <crowd.token_key>=****; Domain=****; Expires=****; Path=****; HttpOnly[\r][\n]

X-Seraph-LoginReason: OUT

Set-Cookie: <crowd.token_key>=****; Domain=****; Path=****; HttpOnly[\r][\n]


0 answers

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events