-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Password too long with Windows authentication #799
Comments
I faced the same issue and it looks like that issue is restricted to the popup dialog. You can disable the gui popup and switch to a text-based prompt with
|
Thx for the answer @ferraith |
The main branch now contains a replacement prompt that should avoid the "too long" problems. |
@usinelogicielle - our secret scanning software detected a token in your description. Here are the recommended remediation steps:
We recommend following these steps immediately. |
@ldennington No worries, this token was created only for this issue. Already deleted in our plateform :) |
Thanks for confirming! |
Which version of GCM are you using?
Which Git host provider are you trying to connect to?
We used gitlab on premise for git and Artifactory on premise for git LFS
Expected behavior
The credential with very long characters saved by Windows is entirely saved in the credential manager.
Actual behavior
I have a very long password given by Artifactory.
When I enter it in the window for Windows to save it in the login manager. The password is not complete. Then during its use, git says that the credential is not good because it is not complete.
If I cancel the window, 2 others open and these ones work well.
It seems the password length is limited to 256 characters but my token has 853 characters.
Logs
The real token is : "eyJ2ZXIiOiIyIiwidHlwIjoiSldUIiwiYWxnIjoiUlMyNTYiLCJraWQiOiJIM01iTXh5U3duM2U2Rm1mRjVMUUNNem1KVmdMWmdtNUkyQ2cweUlLYXFJIn0.eyJzdWIiOiJqZnJ0QDAxZDg2OG1razZ4cXgyMGd5NXl0Y2Yxa2YyXC91c2Vyc1wvdmRsaWItdGVzdC10b2tlbiIsInNjcCI6ImFwcGxpZWQtcGVybWlzc2lvbnNcL2dyb3Vwczp2ZGxpYi10ZXN0LXRva2VuLGF1dGhlbnRpY2F0ZWQiLCJhdWQiOiJqZnJ0QDAxZDg2OG1razZ4cXgyMGd5NXl0Y2Yxa2YyIiwiaXNzIjoiamZydEAwMWQ4Njhta2s2eHF4MjBneTV5dGNmMWtmMlwvdXNlcnNcL3JpY2hhcmNoIiwiaWF0IjoxNjU4MzkwNTg0LCJqdGkiOiI3N2Y2N2VmMS0wOWYxLTRlMTctODEyMC04MmEzNTgyOTY4ZGMifQ.LXL0UWoz7waWYuGJAWVYUe79F6wUF42nvtKgFi_pxcrv3dQCBEn2wOWNbhSgeuOgbqYdijX6xDNnGOF09hRz0CZO2CJ7bxLShpYY-0cI4mKfhJwRnagB6boaMhbuUTNWGk-ajcACjrPdQubTbilII6fy93Nt4nSOzgDp78u7ZDxD8-q8sACAQ9lvOO1oaNUEsbaU-_fjGY4PSOJsYe4tqS-NV7xPf0JkINLthiDZz8FCGrznMVE0vQO5__SfMmy1B5g_eCM-eID3gk9XWhYSL8NR9-d3YgSc1LY86OfitBM3P1ska93qD3viipc_BK4VznrC3oepJKqR8mkeFjcXLQ"
The log is sanitized from personnal info. All change are between <>. The password is shown but already deleted in our instance.
The text was updated successfully, but these errors were encountered: