-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
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
Authentication does not work with for NTLM-authorized git repositories #7084
Comments
What do you set GIT_ASKPASS to to get it to work? Just curious because I have no idea how Kerberos/NTLM works. I think letting GIT_ASKPASS go through if it looks like a sane input might be a good option. Right now we always override it because it lead to issues where git prompts but it's not going through to the user so we end up blocking with a prompt that will never get any input. |
On the one hand, when not using Composer, it just works with any setting because But answering your question while looking at the example from Jenkins CI: they just built a temporary command such as An alternative solution might be to have a configurable whitelist (with entries like, for example |
The problem is, we don't want git to prompt the user on the console, because that won't go through the composer process executor and it'll block there endlessly AFAIK. That's why we provide GIT_ASKPASS echo to make sure that if git prompts it gets "credentials" and then fails hard with invalid credentials so that we can then ask the user ourselves for credentials. I'm still not sure how to best proceed here. |
Closing as nobody cared to fix it in these many years, if still applicable do tell and I will reopen. |
My
composer.json
:Output of
php56 ~/bin/composer.phar diagnose
:When I run this command:
I get the following output: (having configured
auth.json
correctly, but also when entering the credentials by hand)And I expected this to happen:
a successful clone of the dependency :)
Further notes:
Without
composer
, a clone is possible only when user and password are not specified inside the URL.However, it does work when
GIT_ASKPASS
.However: composer does everything that these options do not work:
GIT_ASKPASS
is being unset, andIMO there are these possible solutions:
GIT_ASKPASS
environment variableGIT_ASKPASS
(as Jenkins is doing it, for example) instead of putting username and password into the URL.The text was updated successfully, but these errors were encountered: