WORKAROUND
On March 2, 2022, all OAuth integrations between Git Integration for Jira and Azure DevOps and VSTS were interrupted. Our investigation found that Microsoft OAuth apps’ client secrets expire after 5 years. This limitation has a single workaround and that is — for all customers to reconnect. We apologize for this inconvenience and interruption in service. Below are the steps to reconnect.
Requirements:
-
Jira administrator permissions
-
Azure DevOps / VSTS account or service account.
Steps:
-
Go to the Manage integrations page in the Git Integration for Jira app.
-
Click on the integration name.
-
Click on Reconnect.
-
Login to Azure DevOps / VSTS with the account you wish to associate with Git Integration for Jira Cloud.
Videos:
GIJ Cloud
GIJ Server/DC
If you still have a question – reach out to our Support Desk or email us at [email protected].
Related articles
Why don’t I see commits? (Git Integration for Cloud) (Git Integration for Jira Cloud)
Repositories missing from Azure DevOps (or VSTS) integration (Git Integration for Jira Cloud)
Licensing error – installCheck failed (Git Integration for Jira Cloud)
Why don’t I see the Create branch or pull request features? (Git Integration for Jira Cloud)
Connection error for self-hosted git servers (Git Integration for Jira Cloud)
SSH key file format is invalid (Git Integration for Jira Cloud)
Error while reindexing – Java heap space / Object too large, rejecting the pack (Git Integration for Jira Cloud)
OAuth connection error or error 401 page with Azure DevOps integration (Git Integration for Jira Cloud)
OAuth connection error or error 401 page with Azure DevOps with Active Directory integration
Empty list of repositories after integration of Azure Repos (Git Integration for Jira Cloud)
Reconnecting Azure DevOps and VSTS OAuth integrations (this page)
