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
Next: Root
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.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I've managed to create an Application link for my server-side application, and run through the oAuth dance and get access tokens. This all works fine, and I can use the tokens using the REST API.
However, I've read elsewhere that the tokens have a limited lifetime (e.g. https://answers.atlassian.com/questions/332492) that can be seen in http://<JIRA_URL>/plugins/servlet/oauth/users/access-tokens. However, with my Cloud installation of JIRA, there is no expiry listed on this page - just the date the name of the app, date granted, 'Read and Write access' and a button to revoke.
How can I tell what the token lifetime is?
"You can revoke this access token at any time from your JIRA user account, otherwise, all access tokens expire after seven days."
This is from the documentation.
https://confluence.atlassian.com/jiracoreserver071/allowing-oauth-access-802172493.html
Let me know , if you guys have any useful information.
Looks like this indeed the case for Cloud - see https://support.atlassian.com/jira-work-management/docs/allow-oauth-access/ which was updated in Jun 2021 so is current.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The tokens expire as specified in the "oauth_expires_in" parameter when you get the access token. For example, on a default configured JIRA instance on Atlassian's server is 157680000 (which is 5 years)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Using Atlassian Access, they are configurable.
1. After you log into Atlassian Access, from the top set of tabs, select security
2. from the left hand panel click on session duration
3. In the middle of the screen is a drop down that will allow you to select the length of time that you would like your session token to last for.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
They're lifetime tokens. The documentation you've linked to is slightly outdated I believe ( it contains screenshots from 7 years ago). There are no expiry dates associated with access tokens which you can confirm by viewing access tokens from your JIRA console.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Did you guys get an update to this? If there is no expiry listed there, does that mean it is lifetime?
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.
Hi, i just finished the OAuth tutorial two, and i have the same question!! Even with a standalone server, there is no expiry date mentioned when consulting the token access for a user. Any help? @Kevin Dixon, did you get to solve this? (JIRA servre 7.0.10)
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.