Microsoft OAuth integrations not indexing

Summary

Microsoft OAuth integrations not indexing

This incident has been resolved.

• Started

  Mar 2, 2022 · 5:30 PM

• Resolved

  Mar 5, 2022 · 9:44 AM

• Duration

  2d 16h 14m

• Severity

  Minor

• ◆

  Identified

  Mar 2 · 5:30 PM Git Integration for Jira

  The issue has been identified and a fix is being implemented.

• ◐

  Investigating

  Mar 2 · 6:11 PM Git Integration for Jira

  We are currently investigating this issue.

• ◆

  Identified

  Mar 2 · 6:42 PM Git Integration for Jira

  Microsoft VSTS and Azure DevOps OAuth applications have a bug/limitation where the application secret expires 5 years after creation. This secret cannot be refreshed/updated. The workaround from Microsoft is to create a new OAuth application and have consumer re-connect: https://developercommunity.visualstudio.com/t/client-secret-is-expired-even-after-refresh/1564908 We will be updating production shortly. Once updated, customers will need to reconnect https://cln.sh/26TUNm in the integration settings. If you need assistance with this, please contact support@bigbrassband.com.

• ◉

  Monitoring

  Mar 2 · 11:58 PM Git Integration for Jira

  A fix has been implemented. Customers who use the the OAuth integration type for Microsoft Azure Repos or Microsoft VSTS will need to reconnect. See https://bigbrassband.atlassian.net/wiki/spaces/GITCLOUD/pages/2079686657/Reconnecting+Azure+DevOps+and+VSTS+OAuth+integrations for instructions on how to reconnect.

• ✓

  Resolved

  Mar 5 · 9:44 AM Git Integration for Jira

  This incident has been resolved.