-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
The following policy rules failed: [\"ExpirationRule\"]" #66
Comments
Could we have an extra parameter "-d" or "--debug" to enable |
My initial guess is that this resource requires a limited window of activation (default is 480 min, i.e. 8 hours). Could you retry with the parameter From the help message:
Edit: Based on Common errors returned by Azure Privileged Identity Management API, it seems that the error code XX is indeed due to a limitation in the maximum duration for a given role activation:
Try lowering the duration (e.g. |
I'm working on an improved logging solution with this goal in mind. Stay tuned! |
Thanks, it works after add And I test with After manually check in Azure Console, I found the reason is, in our company, the max Duration is 6 hours ( |
Another problem with When I run the command without Is this the design? If I need activate the rest, I have to run as command
But got a new issue
Updatefor below roles:
I am fine to activate the rest 3, except role of |
I have fixed the issue by add
|
Hi @ozbillwang , I have now implemented a |
Thanks, with |
Welcome
Description of the problem
With latest release, I can list role now.
But when I try to activate the role, I got error
"The following policy rules failed: [\"ExpirationRule\"]"
Version of az-pim-cli
Configuration
export PIM_TOKEN=xxxx
Go environment
Output of command
Validation
The text was updated successfully, but these errors were encountered: