We will always see 401s with the Docker client during the initial authentication request and this is expected. The Docker client sends credentials once the 401 is returned.
|non_authenticated_user|GET|/api/docker/v2/|401|
|user|GET|/api/docker/null/v2/token|200| (the null in this request can also be the repository name we are logging into, but in this request, we are getting a token for the Artifactory registry itself)
|user|GET|/api/docker/v2/|200|
We can further debug to gather a bit more information by mimicking the Docker login via curl (this is repository path specific request, but can be updated for other methods) e.g.
curl -uuser http://PLATFORM_URL/v2/DOCKER_REPO/token -v
|non_authenticated_user|GET|/api/docker/v2/|401|
|user|GET|/api/docker/null/v2/token|200| (the null in this request can also be the repository name we are logging into, but in this request, we are getting a token for the Artifactory registry itself)
|user|GET|/api/docker/v2/|200|
We can further debug to gather a bit more information by mimicking the Docker login via curl (this is repository path specific request, but can be updated for other methods) e.g.
curl -uuser http://PLATFORM_URL/v2/DOCKER_REPO/token -v