Forum Discussion

zachthefrank's avatar
zachthefrank
Frequent Visitor
2 years ago

Git integration issues after Active Directory Password change

Hi all,

 

Up until Friday I had a working Git integration. But then I had to do an Active Directory password change. Now all of my objects read as not synced. When I click on source control I get an error with a meaningless and unsearchable code. When I try to adjust the setting on the connection it says there are no branches available. And if I disconnect the workspace hoping to reconnect, it says there are no Organizations available for me to select. Anyone know how to change/reset/relink your Azure Devops account or another way to resolve this?

4 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi zachthefrank ,

    This might be caused by a mismatch between your credentials and the ones stored by Git or Azure DevOps. Here are some possible solutions you can try:

    • Check if you have a credential helper setup by running git config credential.helper in your terminal. If your remote URL is an HTTPS one, the wrong credentials might have been cached by the helper. You can either update the credentials. Can't push local git to Azure DevOps git repo because of Authentication Failed, but for correct password - Stack Overflow
    • If you’re using personal access tokens (PATs) to authenticate with Azure DevOps, make sure your token has not expired or been revoked. You can create a new token or manage your existing ones from the web portal. You can also use Git Credential Manager to generate tokens automatically when you sign in to Azure DevOps. Authenticate with your Git repos - Azure Repos | Microsoft Learn
    • If you’re using SSH keys to authenticate with Azure DevOps, make sure your key is valid and has the correct permissions. You can test your SSH connection by running ssh -T [email protected] in your terminal. You can also add or remove SSH keys from the web portal. Use SSH key authentication - Azure Repos | Microsoft Learn
    • If you’re using OAuth to authenticate with Azure DevOps, make sure that the third-party application access via OAuth option is set to ON in your organization settings. You can access this option from the Security > Policies section of the web portal. 

     

    How to Get Your Question Answered Quickly 

     

    If it does not help, please provide more details .

     

    Best Regards
    Community Support Team _ Rongtie

    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

     

     

     

  • verify that your repository settting are correctly configured and synchronized properly especially for branch visibility access permission. 

  • Have you signerd out of both services and back in again to refresh the credentials?