You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 15, 2023. It is now read-only.
I have enabled Git credential manager for authenticating credentials. As there are multiple users for the system, I would like the credential manager to prompt for user credential on each push for authentication. When the interactive mode is set to always, the git credential manager asks for the credentials each time, but also generate a new personal access token for the same username and repo. A mail is also triggered each time a token is generated and all these tokens are maintained in the profile settings. Why are new personal access tokens generated each time for the same user credentials and repo. Are the previously generated tokens valid, once new token is generated? If yes, how? Is there any way to stop generating new tokens for the same credentials.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have enabled Git credential manager for authenticating credentials. As there are multiple users for the system, I would like the credential manager to prompt for user credential on each push for authentication. When the interactive mode is set to always, the git credential manager asks for the credentials each time, but also generate a new personal access token for the same username and repo. A mail is also triggered each time a token is generated and all these tokens are maintained in the profile settings. Why are new personal access tokens generated each time for the same user credentials and repo. Are the previously generated tokens valid, once new token is generated? If yes, how? Is there any way to stop generating new tokens for the same credentials.
The text was updated successfully, but these errors were encountered: