The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×
Forums
Home Q&A Discussion groups Articles Ask a question Search
Learning
Events
Champions
Release Notes
Community
Forums
Home Q&A Discussion groups Articles Ask a question Search
Learning Events Champions Release Notes
Forums
Home Q&A Discussion groups Articles Ask a question Search
Learning Events Champions Release Notes

Forums

Articles
Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Q&A
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

Access logs on EC2 Instance to debug Auth issues

Srinivas
Srinivas
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!
Get involved
April 21, 2021

Hi,

Currently our team set-up JIRA DataCenter and attached OIDC Auth as secondary authentication. But was seeing an Error saying "Please contact your administrator. Give them this error identifier:". I am the administrator and trying to see where I should check the logs. If it is on Ec2 instance, I have tried to access log folder on instance but don't have permissions as they were only set to JIRA user. Can I know how I can provide permissions to ec2-user to access logs folder for debugging?

 

Thanks!

Watch
Like Be the first to like this
1668 views

1 comment

Comments for this post are closed

Community moderators have prevented the ability to post new comments.

Srinivas
Srinivas
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!
Get involved
April 21, 2021

Ignore the question! I could have simply used 'sudo chmod'. My bad!

 

Actual Auth issue is due to wrong claim configuration and after using the default ${sub} claim, the issue is fixed.

Like
Reply
groups-icon
Data Center
TAGS
AUG Leaders

Atlassian Community Events

    See all events
    Community
    Forums
    FAQs Forums guidelines
    Learning
    About learning Resources
    Events
    Champions
    Release Notes
    Copyright © 2026 Atlassian
    Privacy Policy Notice at Collection Terms Security