-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
az login
fails: ValueError: Unable to get authority configuration for https://login.microsoftonline.com/9a2e....
#20507
az login
fails: ValueError: Unable to get authority configuration for https://login.microsoftonline.com/9a2e....
#20507
Comments
@jiasli for awareness |
This error is raised from here: if 400 <= resp.status_code < 500:
# Nonexist tenant would hit this path
# e.g. https://login.microsoftonline.com/nonexist_tenant/v2.0/.well-known/openid-configuration
raise ValueError("OIDC Discovery endpoint rejects our request") Indeed, the url derived from the reporter's tenant GUID is Looks like @AnilPeriyedath pasted an incorrect GUID. Can you check that, Anil? P.S.: MSAL Python |
I have merged in the error message improvement in upstream. It will be shipped with next release of MSAL. This issue here can be closed due to inactivity. |
I ran into this issue recently. It turns out I had fiddler open which was messing with the network request. Closing Fiddler fixed the issue |
az login
fails: ValueError: Unable to get authority configuration for https://login.microsoftonline.com/9a2e....
If there is nothing in ~/.azure and you use the interactive login which is directed to the MS Azure login screen, how is this a user error when the wrong tenant id is being configured? Just for clarity. |
Tenant ID is specified by the user via the
That's why it is a user error. If you don't specify
It will never raise this error. |
@jiasli, as you note: If you don't specify --tenant, az login with use a special tenant called organizations: and that behavior, as expected above, was failing no worries, thank you. |
Could you share the full error message you see for us to investigate? |
@jiasli to confirm, this isn't a user error as mentioned by @rjsalicco, is it? The CLI docs list Is this coming from MSAL? Do you know where I can find further information on the source of this issue? |
Jiasli already described it here.
We might not have tested this corner case. Do you have log to share, @angustatchell ? |
@rayluo thanks for getting back. I have opened a ticket with Azure support too because I can still see this deleted tenant ID showing up as a linked AD directory in my AZ Portal. (I don't know if this might indicate the problem is upstream of the AZ CLI / MSAL). This is autogenerated. Please review and update as needed.Describe the bugCommand Name Errors:
To Reproduce:Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
Expected BehaviorEnvironment Summary
Additional Context |
@angustatchell, could you run
If it returns a deleted tenant, this should be checked by ARM service (Azure support) since this looks like caching issue. |
Hi @jiasli I see in debug output that the call to the Tenants List API returns a list of objects for my current tenants AND the deleted tenant as well. The request url from my CLI is: The existing tenant objects have keys for: However, the deleted tenant returned only has keys for: All the tenants have their Would that indicate the problem is indeed from the ARM service? |
Yes. You may share the HTTP trace with Azure support to help them check why deleted tenant is still returned. |
This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az login
Errors:
To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
az login --service-principal -u {} -p {} --tenant {}
Expected Behavior
Environment Summary
Additional Context
The text was updated successfully, but these errors were encountered: