-
Notifications
You must be signed in to change notification settings - Fork 886
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
Dependency Resolution Broken On Authenticated Sources #2057
Comments
Hi @rgrwatson85, thanks for logging this and I'm sorry this is occurring for you. Thanks for including the logs - no chance that you have a load balancer in front of this? |
@ferventcoder We do have a private load balancer in front of artifactory, and an application gateway in front of the load balancer. I have tried targeting the repo from all angles by pointing the source at the public gateway, the private load balancer, and the individual virtual machines hosting artifactory. Seems to not make a difference. I also tried using your branch for the PR for updating NuGet.Core package to the latest, and that also failed. |
Just so I'm clear, as part of your testing, you targeted artifactory directly in there without any load balancer or anything in the way? |
@ferventcoder That is correct. The logs that i sent you were from when I was targeting the public endpoint. But I updated the config file to point at one of the servers directly and got the same results. |
Thanks. That will be helpful. |
@ferventcoder Please let me know if there is anything I can do to help. |
What You Are Seeing?
When installing packages that have any dependencies, we are getting 401 response codes back when starting the dependency walking process. For example installing nodejs will fail once nodejs.install begins to be resolved. If we install the dependency packages first, and then install the target package it works.
WORKS:
choco install nodejs -i
WORKS:
(choco install nodejs.install -y) -and (choco install nodejs -y)
WORKS:
choco install nodejs.install nodejs
FAILS:
choco install nodejs
ALSO WORKS:
nuget install nodejs -OutputDirectory $env:ChocolateyInstall\lib
choco install nodejs --force
What this means to me, is that our credentials are good and that either Choco, or the Nuget.Core package being used by Choco, is failing once the challenge/response authentication cycle starts. The first 401 response it gets back due to not having sent an Authorization header causes a failure instead of initiating a second request with the proper headers.
What is Expected?
We do expect to see 401 responses from the repository since we are using an authenticated repository. We also would expect that if we can install packages without dependencies with no authentication issues then we would be able to install packages with dependencies as well.
How Did You Get This To Happen? (Steps to Reproduce)
We have virtual repositories setup, but for now are linking directly to the remote repository as we have seen that there are open issues using chocolatey on virtual Artifactory repositories.
Output Log
Full Log Output
Full Trace Log Output
The text was updated successfully, but these errors were encountered: