Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

What is error 15e849eb-8130-44bf-9f4b-f4d11c86819c

taylor_vidal-ext
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 21, 2026

What is error 15e849eb-8130-44bf-9f4b-f4d11c86819c

  and how does a Jira Administrator resolve this issue?

 

We can't log you in  right now. Please contact your administrator. Give them this error identifier.

4 answers

1 vote
Viswanathan Ramachandran
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
August 21, 2026

Hi,

Can you give us more details?

Where do you see this error? On what prompt or operation?

taylor_vidal-ext
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 21, 2026

Screenshot 2026-08-21 161016.png

taylor_vidal-ext
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 21, 2026

This is the screenshot and error is after the log on

Viswanathan Ramachandran
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
August 21, 2026

This is likely SSO login issue or the user is deactive or missing access. 

If you're organisation admin..

  • Go to admin.atlassian.com - security - identity providers or SAML and make sure certificate usually x509 is not expired
  • Go to Directory - Users, search for the user, and verify they are listed as active with Jira Software

 

0 votes
said kouzibry
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
August 21, 2026

I understand that you might think the code you're getting is useful to ask the question. What I don't understand are the people asking you for screenshots, those would be completely useless.

The code you're getting is an identifier, it helps you find the relevant log lines in the log file. copy the code, open your atlassian-jira.log and atlassian-jira-security.log files, use this link to find them, "log" part https://confluence.atlassian.com/adminjiraserver/important-directories-and-files-938847744.html

Then once you find the relevant part, you can anonymize it (remove emails, full names or other personally identifying information ) and send it to us here. From there we will have a better idea on where to look next.

0 votes
Tinker Fadoua
Community Champion
August 21, 2026

@taylor_vidal-ext 

A screenshot would be very helpful once you hide confidential information, or if you can elaborate little bit more.

Best,

Fadoua

0 votes
Varun Chillamcharla
Contributor
August 21, 2026

Hi Taylor,

This usually happens during SSO/login failures (misconfigured SAML, expired certificate, IdP-side issue, or a mismatch between your identity provider and Atlassian's config). Since it says "contact your administrator," that ID is meant to be handed to your Org Admin so they can look it up in the SSO/authentication audit logs at admin.atlassian.com under Security > Authentication policies, or raise it with Atlassian Support directly, only they or your org's SSO logs can actually trace that identifier to the real cause.

Agreeing with @Viswanathan Ramachandran, more context would help too, is this happening for one user or everyone, and did it start after any recent SSO or IdP change on your end?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
ENTERPRISE
TAGS
AUG Leaders

Atlassian Community Events