When do JIRA oAuth tokens expire?

[Kevin Dixon]

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?

[timotei]

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)

[Yousef Hammouda]

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)

[Kevin Dixon]

@Yousef Hammouda - no, I didn't find a solution to this yet.

[Suket Sharma]

Did you guys get an update to this? If there is no expiry listed there, does that mean it is lifetime?

[Swastik Roy]

"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. 

[Suket Sharma]

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.