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

Unable to login with LDAP active directory after upgrade to 8.22.3

I upgraded Jira Core to 8.22.3 and I am now unable to login with my active directory accounts.  

I logged in with the recovery account and test the remote directory connection.  All of the steps complete except the user authentication.  I get this error:


Test user can authenticate : Failed
org.springframework.transaction.CannotCreateTransactionException: Could not create DirContext instance for transaction; nested exception is org.springframework.ldap.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C090439, comment: AcceptSecurityContext error, data 57, v4563]; nested exception is javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C090439, comment: AcceptSecurityContext error, data 57, v4563]
For more information regarding LDAP error codes see Troubleshooting LDAP Error Codes.
I tried resetting my service account's password with no effect.  The user passwords are correct and can authenticate as regular logins.

5 answers

I'm experiencing the same issue after the update to 8.22.3 ...

All of my users can't connect to jira anymore since this afternoon !

Is there a quick fix or a workaround ? 

  • Update: reverted to my previous version and it's fine. Thinking I'll either try again or update incrementally until it breaks. 
Like # people like this

Thanks for this temporary fix !!

0 votes
Gonchik Tsymzhitov
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 01, 2022

Nice shot! :) 

The suggested workaround also worked for us, thanks a lot for this!

Update 2: Used Monjal Patel's workaround link and it worked.

  1. Updated to 8.20.8 (i wanted to be sure my version of files were not too far out of date)
  2. Replaced the DefaultApplicationRoleManger files in the web-inf folder per


From the link:

2) Permanent Solution: Copy/ Replace the old files of 8.20.8 or earlier in directory "/atlassian-jira-software-8.20.9-standalone/atlassian-jira/WEB-INF/classes/com/atlassian/jira/application"



On update to 8.20.9 the error occurred again.  On replacement of the files I was able to login.

Copying the file javax.crypto.spec.SecretKeySpec_1649567443152 from old backup did the job irrespective it has different name , this worked as it belonged to same instance but existing on old infra 

Like Gonchik Tsymzhitov likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events