-
Bug
-
Resolution: Fixed
-
Critical
-
None
-
Windows server 2012 R2
git-client-plugin 2.0.0
Git client plugin 2.0.0 seems to have swapped from using .gitcredentials to GIT_ASKPASS and when I have an & character in my password the authentications fails. 1.21.0 was fine (and reverting to that version swaps back to using .gitcredentials)
Escaping the & in the password stored in the credentials by using ^& works round the issue (but if the same credentials are used elsewhere then they will break)
- is duplicated by
-
-
- Closed
-
- is related to
-
-
- Closed
-
-
-
- Closed
-
[JENKINS-38194] Ampersand in Git password causes authentication failure
| Description |
Original:
Git client plugin 2.0.0 seems to have swapped from using .gitcredentials to GIT_ASKPASS and when I have an & character in my password the authentications fails. 1.21.0 was fine (and reverting to that version swaps back to using .gitcredentials) Escaping the & in the password stored in the credentials by using ^& work round the issue (but if the same credentials are used elsewhere they will break) |
New:
Git client plugin 2.0.0 seems to have swapped from using .gitcredentials to GIT_ASKPASS and when I have an & character in my password the authentications fails. 1.21.0 was fine (and reverting to that version swaps back to using .gitcredentials) Escaping the & in the password stored in the credentials by using ^& works round the issue (but if the same credentials are used elsewhere they will break) |
| Description |
Original:
Git client plugin 2.0.0 seems to have swapped from using .gitcredentials to GIT_ASKPASS and when I have an & character in my password the authentications fails. 1.21.0 was fine (and reverting to that version swaps back to using .gitcredentials) Escaping the & in the password stored in the credentials by using ^& works round the issue (but if the same credentials are used elsewhere they will break) |
New:
Git client plugin 2.0.0 seems to have swapped from using .gitcredentials to GIT_ASKPASS and when I have an & character in my password the authentications fails. 1.21.0 was fine (and reverting to that version swaps back to using .gitcredentials) Escaping the & in the password stored in the credentials by using ^& works round the issue (but if the same credentials are used elsewhere then will break) |
| Description |
Original:
Git client plugin 2.0.0 seems to have swapped from using .gitcredentials to GIT_ASKPASS and when I have an & character in my password the authentications fails. 1.21.0 was fine (and reverting to that version swaps back to using .gitcredentials) Escaping the & in the password stored in the credentials by using ^& works round the issue (but if the same credentials are used elsewhere then will break) |
New:
Git client plugin 2.0.0 seems to have swapped from using .gitcredentials to GIT_ASKPASS and when I have an & character in my password the authentications fails. 1.21.0 was fine (and reverting to that version swaps back to using .gitcredentials) Escaping the & in the password stored in the credentials by using ^& works round the issue (but if the same credentials are used elsewhere then they will break) |
username/password yes, using http not https (internal stash server)
karmseever, you might be right with this being a similar issue that I was having in JENKINS-38179, I dont have a "&" character in my password but I do have a ")" and a "^".
Pretty certain the "^" would have broken it, which means this is effectively a duplicate of yours.
Under certain circumstances (Delayed Expansion has been enabled in the command session) '!' will also have the same issue
| Link |
New:
This issue is related to |
| Link |
New:
This issue is related to |
karmseever are you using a username / password (as used with https based git repository access) where the the password contains the "&" character, or are you using a private key protected by a passphrase where the passphrase contains the "&" character (as used for ssh and scp based git repository access)?