You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Join now to unlock these features and more
I have created an app in developer console where I have added authorization 3LO OAUTH2.0 , in the authorization url added offline_access in the scope.
On the official documentation https://developer.atlassian.com/cloud/confluence/oauth-2-3lo-apps/ the refresh token expiration details are mentioned.
90 days - Inactivity expiration
365 days - absolute expiration
On the same doc we have OAuth0 by okta documentation where we can disable the expiration of refresh token, Is there a way in atlassian OAuth2.0 apps where we can disable the expiration of refresh token?
The refresh token from Atlassian is a rotating one and not persistent. However, there's no configuration within the developer console that disables the refresh token. I believe the docs mention using the dashboard from auth0 directly. Although, I'm not certain how that works. Typically, I would say that as long as the user remains active within a 1 year period the refresh token won't be invalidated.