Cannot delete access policies that were auto-generated during the migration to 2.4
To be able to delete an Access Policy:
1 - Go to the Management page for the Policy in question.
2 - Verify that System is "N" and Active is "N" and Assigned count is "0". To delete a policy it must be inactive, not assigned to anything and not a system policy * (see below)
3 - This can also be verified on the Details tab with the System and Active checkboxes. Which should be unchecked.
4 - The Used By tab should be empty.
If you have trouble deleting a policy, it may still be in use. To find what request is using the policy, in /PAR go to Request > Session > Manage Requests or Request > Password > Manage Requests and on the Listing tab you will see an "Access Policy" column. This is where you can verify which Access Policy is assigned. The logs will cycle with age, after which you can remove that auto policy.
In order for the "Request" menu to appear in /PAR, you need to be assigned Requestor permission to at least one account. This rule applies to Administrators as well. For example, if you are logged in as the user paradmin, simply grant yourself Requestor permission to any account and then reload the page. You should then see the Request menu between the Review and Reports menu.
Global setting for changing retention Period:
Retention Period – File Release Log
Retention Period – File Release Request
Retention Period – Password Release Log
Retention Period – Release Request
Retention Period – Session Request
© 2024 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center