Skip to content
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

Artifactory without enabled "anonymous access" doesn't use revisions #5687

Closed
lasote opened this issue Aug 29, 2019 · 1 comment
Closed

Artifactory without enabled "anonymous access" doesn't use revisions #5687

lasote opened this issue Aug 29, 2019 · 1 comment

Comments

@lasote
Copy link
Contributor

lasote commented Aug 29, 2019

If the "anonymous access" is not enabled in Artifactory, the "ping" Conan endpoint returns a 401 if no authentication is sent, so the capabilities are never read, but the 401 is currently ignored by the client, storing an empty set of capabilities for the remote.

To fix this, we have to raise an exception if we receive a 401 in the "ping" endpoint so we force the authentication process in the client. But there is another issue to solve: the authenticating process in the client is trying to get the capabilities to know if it should use v1 or v2 so it is like a snake biting its own tail.

It can be fixed by using always "v1" to authenticate and not hiding the 401 in the ping endpoint.

@lasote
Copy link
Contributor Author

lasote commented Aug 30, 2019

Fixed, will be released at 1.18.2

@lasote lasote closed this as completed Aug 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant