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
Interests
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,556,526
Community Members
 
Community Events
184
Community Groups

Unable to validate JWT access token generated through OAuth 2.0 flow

Edited
Nikhil Dhiman
Nikhil Dhiman May 02, 2023

In one of our applications, we are using OAuth 2.0(3LO) flow for authentication purpose. We can generate JWT access token by going through the steps mentioned here: https://developer.atlassian.com/cloud/confluence/oauth-2-3lo-apps/.

 

Now to check if JWT token is valid or not, we can use https://auth.atlassian.com/ as an authority and audience as a ClientId of registered OAuth app. We were able to validate token till day before yesterday with these configurations. From yesterday with the same authority it is saying Issuer validation failed.

Do we need to change the authority to validate the token now? Any particular changes happened around this ?

Comment
Watch
Like Be the first to like this
223 views

1 comment

Nikhil Dhiman
Nikhil Dhiman May 03, 2023 • edited

Again yesterday it was working with the same configurations and today again not working.

 

I don't expect unstable infra stuff from organization like JIRA Atlassian.

Like
Reply

Comment

Log in or Sign up to comment
Jira
Jira
TAGS
AUG Leaders

Atlassian Community Events

See all events