-
Notifications
You must be signed in to change notification settings - Fork 97
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
UPN cannot access same subscription as GUI login #32
Comments
Looks fine here using ARMClient v1.2.0.0:
Are you sure the password isn't tripping up the PowerShell parser? Do you have the same results in |
I do get the same error in cmd. Is there some way to encode or encapsulate the username and password so that odd characters don't confuse anything? Looking at it now, it returns really quickly (within 1 second, including VPN latency). whereas calls to |
What happens if you don't pass in the password? You should get a |
It fails the same way. |
Alright, looks like i can repro. Let me take a closer look at what's going on. |
It seems to be coming from: BaseAuthHelper.GetAuthorizationResultByUpn, on the line:
|
Is it possible that I need to pass a custom tenant Id in when trying to create the authority for accessing a |
Yes, the ADAL library doesn't seem to like that. @suwatch, @ahmelsayed is this by design? |
In my case the tenant is [TenantGuid] ([TenantName].onmicrosoft.com) The user is a personal hotmail account. I'm not sure about how the hotmail account has permissions to our tenant AD's OMS instance. I am not an azure administrator, nor an AD administrator. |
If I login using the GUI
ARMCLIENT.exe login
, I get 2 tenants, the second of which has a subscription. If I login using upnARMCLIENT.exe upn [user] [password]
I cannot see the subscription. It just saysThere is no login token. Please login to acquire token.
I'm a little confused as to why the UPN doesn't see as much as the GUI login.The subscription in question is currently awaiting payment, but that should affect both authentication methods, correct?
I suspect UPN is a little-used edge-case. I'm trying to avoid making people go through the Azure Active Directory Application registration process. Thank you for your time, and your wonderful tool.
The text was updated successfully, but these errors were encountered: