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.
Hi,
Can you give us more details?
Where do you see this error? On what prompt or operation?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is the screenshot and error is after the log on
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is likely SSO login issue or the user is deactive or missing access.
If you're organisation admin..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
A screenshot would be very helpful once you hide confidential information, or if you can elaborate little bit more.
Best,
Fadoua
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.