Authentification to Azure Container Registry / azurecr.io does not work as it should

[marcohald]

• What problem are you trying to solve? Create a Docker Proxy for a private Azure Container Registry which needs basic auth
• Do you have a workaround you are using at present? No
• What feature or behavior is this required for? A working authentification like the Docker Client
• How could we solve this issue? (Not knowing is okay!) As far as I have seen, the difference between the Auth Request from Nexus and the Docker Client is, that nexus does not send the "account" in the URL as the Docker Client do. This seems to result in a Token that has no Access Redacted Login of the Docker Client Redacted Response of the Docker Client Redacted Login of Nexus: Redacted Response of Nexus:

Redacted JWT Token (left Docker right nexus) As you can see here the entire access array is empty for nexus.

• Tell us about your Nexus Repository deployment: what version, operating system, and database are you using? Nexus/3.64.0-04 (OSS; Linux; 6.1.0-18-amd64; amd64; 1.8.0_402)
• Anything else?

[nblair]

Thanks for opening an issue @marcohald. I'm not 100% positive we fully support proxying Azure Container Registry at present, as evidenced by the detailed investigation. We'll have to review what's possible and report back; it may need to be an enhancement request.

[marcohald]

Sorry for opening this Issue. I tried to add the account parameter with a intercepting proxy and then recognized that i still get no valid token. I rechecked everything and spotted a Typo in the Image Name. Sonatype Nexus seems to be fully compatible to Azure Container Registry.