Question
Eviden
NL
Last activity: 2 Jan 2025 11:42 EST
ARO on Rule-Declare-Pages is returning not expected result
Issue
For a use case we need to block most Data Pages and only a few should be allowed. Now we can use the security tab by introducing multiple privileges, however we are looking for a easier solution via ARO's to implement.
In testing this solution, we wanted to first block all declare pages instances. By using the following ARO:
|
Issue
For a use case we need to block most Data Pages and only a few should be allowed. Now we can use the security tab by introducing multiple privileges, however we are looking for a easier solution via ARO's to implement.
In testing this solution, we wanted to first block all declare pages instances. By using the following ARO:
|
However, we are experiencing no blocking of these instances as expected. Please assist :)
HCLTech
US
@Bob Reawaruw Update the Access group to move the Access role which contains your ARO to top of the order and then check the below checkbox
HCA Healthcare
US
To block most Declare Pages and allow only a few, using AROs (Access Role to Object), set all permissions (read, write, delete, execute) for Rule-Declare-Pages to 0 in the ARO. Ensure the correct role is assigned to the relevant Access Group and test with a user having only that role. If it doesn't work as expected, check for cached rules and clear the cache using Admin Studio. Use Tracer to see if the pages are accessed indirectly. Alternatively, assign privileges on the Security tab of each allowed Declare Page or use a custom decision rule (like an Access When Rule) to control access dynamically. Ensure no conflicting roles or inheritance issues override your ARO settings