The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
× Create
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Community resources
Community resources
Community resources
Oauth 1.0 token expiration and 'refresh'
gpako
I'm New Here 
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 2, 2020 edited
A client of mine needs an app that will modify jira data using oauth1.
Coding an automatic ‘refresh’ similar in user experience to oauth2 would take some time, and if the expiration value is not possible to change from 5 years then the time investment is definitely not worth it.
Can the 5 years expiration be modified via jira config or any other way by an admin? Does it make sense to deal with expiration in any way?
Any help appreciated.
0 answers
Comments for this post are closed
Community moderators have prevented the ability to post new answers.
Community showcase
Atlassian Community Events
Copyright © 2026 Atlassian