Skip to content
This repository has been archived by the owner on Oct 24, 2023. It is now read-only.

ACS-Engine CLI requires an admin to grant permission to access resources in your organization #143

Closed
Grisson opened this issue Dec 14, 2018 · 7 comments
Labels

Comments

@Grisson
Copy link

Grisson commented Dec 14, 2018

Is this a request for help?:
Yes

Is this an ISSUE or FEATURE REQUEST? (choose one):
ISSUE

What version of aks-engine?:
Self build from code

Kubernetes version:
1.12

What happened:
I try to run /aks-engine deploy. It asks me to login in browser. I login with my microsoft.com account.

ACS-Engine CLI needs permission to access resources in your organization that only an admin can grant. Please ask an admin to grant permission to this app before you can use it.

Following is the detail error message.

Request Id: 87ffe193-e50b-46c8-a868-456de5590100
Correlation Id: 4e24354e-cdb3-4c40-9808-c58793c84102
Timestamp: 2018-12-14T00:02:17Z
Message: AADSTS90094: An administrator of Microsoft has set a policy that prevents you from granting ACS-Engine CLI the permissions it is requesting. Contact an administrator of Microsoft who can grant permissions to this application on your behalf.

What you expected to happen:
Let me login and create cluster based on me definition file.

How to reproduce it (as minimally and precisely as possible):
Deploy a cluster with microsoft.com account. Create service principal under microsoft.com tenant.

Anything else we need to know:
It happens on microsoft.com tenant.

@CecileRobertMichon
Copy link
Contributor

@tariq1890 is this the same thing you encountered or is it a different issue?

@tariq1890
Copy link
Contributor

Yes. We need to overhaul our authentication method for deploy. No new users will be able to use deploy with the current deviceAuth method

@Grisson
Copy link
Author

Grisson commented Dec 18, 2018

@tariq1890 Is there a workaround for this issue?

@tariq1890
Copy link
Contributor

@Grisson You would to do an acs engine generate and an az deploy to get around this . This is the only workaround I am afraid.

If you have questions about this flow of commands, please don't hesitate to reach out :).

@Grisson
Copy link
Author

Grisson commented Dec 19, 2018

Got it.
But, how can I scale the cluster?
The acs engine scale command also asks for admin permission. And, if I scale the cluster in the portal, the new nodes will not show up in the cluster.

@tariq1890
Copy link
Contributor

tariq1890 commented Dec 19, 2018

@Grisson can you try this ?

acs-engine scale --auth-method client_secret --client-id <"your SP_CLIENT_ID> --client-secret <"your SP_CLIENT_SECRET"> (other arguments where applciable)"

@CecileRobertMichon
Copy link
Contributor

Closing because of #231

#238 will also bring a new auth method.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants