-
Notifications
You must be signed in to change notification settings - Fork 45
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
Request Access fails #83
Comments
Is it possible that you selected more than 10 roles at once? The "At least one role is required" error can either mean that you didn't select any roles, or that you exceeded the limit of 10 roles. I'll fix this check so that it returns different error messages in the two cases. |
Ahh yes I was trying to go more than 10 roles. Is that limit configurable? |
It's a hard-coded limit currently, but we could make it configurable. The only concern is that it activating 10+ roles might take several seconds. |
I think thats ok as long as it lets the user know its working on it |
I've changed this hardcoded limit from 10 to 30 and activated 20 roles in a bulk. Activation process was a little bit longer, but still faster than for example activation Contributor role via PAM in Azure. So imho this limit could be changed from 10 to 30 for example + proper notification should be visible ( maybe with some time counter ? ). If somebody needs to grant more than 30 predefined roles, it might be good idea to create custom role and use custom roles with proper permissions. |
FYI @jpassing This is the support case I raised for the weird https_proxy traffic hitting the vpc policy |
I added an option/environment variable The change is available in |
After selecting a bunch of roles when I go to request the access i get the following:
When I then go look into the logs i see:
So I think the self activate endpoint is not succeeding so it thinks I have no role selected? Not really sure hoping @jpassing can point me in the right direction.
The only other warning I can see in the logs is:
But since i'm not using the multiparty approval just yet I think this is to be expected since i haven't set it up.
The text was updated successfully, but these errors were encountered: