Deprecation of Persistent Refresh Tokens

[Ian Mitchell]

A colleague received what I see as a marketing email regarding the changing over of refresh tokens. Is this actually happening and is there any impact if there is a change?

I have had no notification from Atlassian on this and guess it is just a marketing ploy

Thanks in advance for any advice!!

Deprecation of Persistant Refresh Tokens support and the impact on the Qualify interface

If you are a user of Atlassian Jira you will probably be aware that they are deprecating Persistent Refresh Tokens support in Oauth, the protocol used to access Atlassian applications.   If you use Oauth to access Jira, which will almost certainly be the case if your Jira instance is in the Jira Cloud, from December 1, 2021 Persistent Refresh Tokens in Oauth will no longer work and the protocol needs to be migrated to Rotating Refresh Tokens, which is a more secure method.  If you have taken advantage of Jira Integration from Qualify, this will affect the interface between the two products as Qualify uses Oauth to connect to your designed Jira Instance.   An update is available to download from Origsoft.com which can be applied to the Bertie 2 (build 7063) or a later release; it uses the new Rotating Refresh Tokens method.

[marc -Collabello--Phase Locked- · Accepted solution]

@Ian Mitchell Yes, the refresh token change is actually happening: https://community.developer.atlassian.com/t/4-aug-2021-action-required-deprecating-persistent-refresh-tokens/50348

However the impact depends on the apps you use.