Comment 11 for bug 1242476

I suspect, but am not 100% sure, that in Juju 1.16 the endpoint matching was sensitive to trailing "/". So the json metadata contains an endpoint with a training "/" but the configured auth url doesn't. Try adding a "/" to the auth url in the environment config, or remove the "/" from the json metadata and see if that helps. If it doesn't work, we'll need to dig a bit deeper.