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: 
Sign up Log in
Products
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

Join now to unlock these features and more

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.

Get started Tell me more
Atlassian Community about banner
4,642,096
Community Members
 
Community Events
196
Community Groups

Access logs on EC2 Instance to debug Auth issues

Srinivas
Srinivas Apr 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!

Answer
Watch
Like Be the first to like this
351 views

1 answer

1 accepted

Suggest an answer

Log in or Sign up to answer
0 votes
Answer accepted
Srinivas
Srinivas Apr 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.

Reply
groups-icon
Data Center
TAGS
AUG Leaders

Atlassian Community Events

See all events