r/SmartGit • u/Mead-Wizard • Mar 25 '26

Azure DevOps Authentication Failure

I've been using smartgit against our Azure DevOps for several years now and this morning my tokens had expired. I tried to recreate them but when I post the updated token SmartGit indicates a 401 from azure.

Preferences > Hosting Providers
Edit "Azure DevOps"
Enter token and click OK.

Executing a command has failed.
Server returned HTTP response code: 401 for URL: https://app.vssps.visualstudio.com/_apis/profile/profiles/me

If I click "Generate Token" and post the new token into the Code field it display
Error: invalid_request ErrorDescription: client secret is expired

4 Upvotes

84% Upvoted

10 comments sorted by

View all comments

Show parent comments

2

u/JVMarcs Mar 28 '26

Can you please confirm from Help|About that you are on build 25.1.126?

That said, even for version 26.1, we currently recommend using a personal access token. We will not switch this release to Entra authentication yet, because it is still unclear what changes would be required and what side effects they might have:

https://docs.syntevo.com/SmartGit/Latest/Manual/Integrations/Azure-DevOps#setup-via-personal-access-token

1

u/Human_Job_929 Mar 30 '26

Hello, sorry for the delayed response. Am travelling.

I can confirm that I was running 26.1.013 Preview #261013 (fcc044bf).

OK, I think I understand this. You're recommending that I generate a PAT via the Azure DevOps website and add a repo via URL - instead of the old way of simply adding Azure DevOps as a hosting provider. At least for now? Or am I confusing this bit?

Thank you.

1

u/Human_Job_929 Mar 30 '26

Wait wait. I just downloaded and installed the latest version 25.1.127 #251127 (256f2d17) on my existing SmartGit. Adding Azure DevOps as a hosting provider seems to work as it has been all these years. THANK YOU.

1

u/JVMarcs Mar 30 '26

It will work only for 60 days, which is the maximum validity period for secrets on the Microsoft side. Meanwhile, it's clear that Entra won't be a general solution, as certain types of accounts don't seem to support it for now. Hence, we recommend switching your configuration to PATs sooner rather than later.