You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: