Closed lydemann closed 2 years ago
Managed to fix this by setting dummy refresh token
better-vsts-npm-auth config set refresh_token DUMMY
Maybe a reset cmd should be in the cli?
idk... if you're in a state where you want to reset your azure creds I'm not sure providing a "reset" command as a wrapper over deleting the refresh_token solves more problems than it creates by mixing the auth principals represented in the file. For those who find them in such a predicament running --help
should lead them to config delete
or another solution like you found.
I can't update the credentials for Azure to use to generate the access tokens.
Even when following this guide for vsts-npm-auth, credential are still persisted:
https://stackoverflow.com/questions/43840562/update-vsts-npm-auth-with-new-username-and-password