Skip to content
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

Undocumented access requirements #20

Closed
anderius opened this issue Dec 4, 2020 · 4 comments
Closed

Undocumented access requirements #20

anderius opened this issue Dec 4, 2020 · 4 comments

Comments

@anderius
Copy link

anderius commented Dec 4, 2020

I have created a service principal, and added it to a group that is administrators in the AKS cluster (using AAD RBAC).

Still, it requires some additional access to log in:

Error: ***"error":***"code":"AuthorizationFailed","message":"The client 'XXXX' with object id 'XXXXXX' does not have authorization to perform action 'Microsoft.ContainerService/managedClusters/accessProfiles/listCredential/action' over scope '/subscriptions/XXXXX/resourceGroups/XXXX/providers/Microsoft.ContainerService/managedClusters/XXXX/accessProfiles/clusterAdmin' or the scope is invalid. If access was recently granted, please refresh your credentials."***

It would be nice if the required access was documented, or maybe I am doing something wrong here?

The required action listCredential, I am not sure about that. :-)

@anderius
Copy link
Author

anderius commented Dec 4, 2020

Hmm.. It only happens the second time I use the action in the same job. For different clusters. I think I should investigate more, and will close for now.

@anderius anderius closed this as completed Dec 4, 2020
@Waidmann
Copy link

Hi @anderius I'm facing this issue now and was wondering if you ever got to the bottom of this?

@anderius
Copy link
Author

@Waidmann I am afraid it is too long ago for me to remember, and I am not working with the project where the issue was anymore. Sorry I could not be of any help!

@Waidmann
Copy link

Thanks anyways :) I will update once I find a workaround/fix!

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

No branches or pull requests

2 participants