ACR does not support logging in with an application identifier_uri about acr HOT 4 CLOSED

One challenges here seems to be the scheme separator : .
The basic authentication header uses the first : as the username and password separator since passwords can contain :. We need to handle the fact that if the first : might be prefixed with a scheme and then use the next : in this specific case.

from acr.

Why does it not take a JSON blob and then deserialize and pull out the values?

The problem gets even harder than you describe since my password could contain a : (colon) character, right?

from acr.

I guess the issue is how the Basic Auth header is created by the CLI . The docker CLI just joins the username and password with a :. So basically we need to handle the client_id as a special case.

from acr.

Given that we are going to support AAD auth, I don't think we might not fix this at this point. Might be worth coming back at some point.

from acr.