Before you start
- Use an isolated app or test tenant, two test accounts with comparable starting permissions, and a separate administrator. Record the app name, tenant and original assignment.
- Pick a harmless page in the receiving app that both accounts can try to open. Start each test in a fresh browser session.
Data and access
OneLogin
Assign the app to a test role and add only the intended test user. Check the app’s Users list for the assignment. After removing the role from the test user, look for a direct assignment or a second role before retrying the app.
Check. The app lists the test user before the role removal. Record any remaining assignment before testing access again.
Duo
On the test application, set User access to Enable only for permitted groups and select the test group. Confirm both test users have Active status. Check the effective policies before testing because Bypass users, Skip MFA rules and policies for unknown users can change the result.
Check. The included and excluded active users get the expected outcomes. Record any effective policy exception if their results differ.
CyberArk
On a test web app in CyberArk Identity, inspect the application’s Permissions. Check which test users can run it and whether it is automatically deployed to their portals. Open the receiving app with both accounts to check any role granted by the destination.
Check. Check portal visibility and destination role independently for both users. Record which one can open the expected app page.
Oracle
In the intended Oracle Cloud Infrastructure identity domain, assign the test application to a test group. Verify the selected domain and group membership. Check for direct assignments or another group if access continues after you remove the test membership.
Check. The assignment names the correct identity domain, app and group. Confirm the outcome from the test user’s app session.
miniOrange
In the test SAML app, open Policies and check the groups assigned to the app and the policy applied to each. Try the same app with a user in the test group and one outside it. Recheck the app after withdrawing the test assignment.
Check. The included user reaches the test app and the excluded user does not. Check again in a fresh session after removing the assignment.
SailPoint
In Identity Security Cloud, inspect the test access profile and its source entitlements. Check the test identity’s Access History before and after a scoped change. Confirm the actual entitlement on the connected source and retry the app after the change reaches that source.
Check. Access History shows the scoped change, and the source shows whether the entitlement was applied or removed.
Check both identities at the destination
Record which test account reached the expected page, which was denied and whether removing the test assignment changed the result. Record any separately granted access you found. Restore the original assignments when you finish.
Check. The record includes both destination outcomes before and after the change and confirms the separate administrator still has access.
Check your result
The test app reports the expected access for both accounts before and after the assignment change. The separate administrator can still reach the provider and receiving app.
If you get stuck
The account still opens the app
Start a fresh session at the destination and check other active assignments. If the provider manages the app’s entitlement through provisioning, confirm the destination received the change before drawing a conclusion.