Check that a test account lands in the right app

Follow a test account through the provider and into the intended app. Confirm the account, the app role and the administrator’s recovery path.

Before you start

  • Use a non-production provider and destination where you can test the full flow. Check the app or tenant name and keep a working administrator who can reach the destination separately.
  • Use a new browser session for each test. Record only the expected test identity, role and destination. Keep raw assertions, cookies and identifying attributes out of screenshots and notes.

Data and access

Shared or checked
The destination app receives an identity from the configured provider and maps it to an application account or role.
Check separately
Check direct administration, local recovery, and any groups or roles managed inside the destination app separately.
  1. PingFederate

    Select the test service-provider connection and check its enabled browser profiles. Start from the app for a service-provider-initiated profile. Start from the identity-provider link only for a profile configured to accept it. At the destination, confirm which account and role opened.

    Check. The app shows the expected test user and role after you start from a supported entry point.

  2. NetIQ

    For NetIQ Identity Manager 4.9 Identity Applications, review the SAML configuration connecting One SSO Provider (OSP) to Access Manager. Use the test application’s own entry URL. Verify that it opens the expected Identity Applications account and that the account can read only the intended test page.

    Check. The test user opens the intended Identity Applications page and cannot reach the test action outside their role.

  3. Shibboleth

    In Shibboleth IdP 5, use the AACLI resolver test for the disposable principal and the exact app entity ID. Review the expected released attributes. Then open the test app in a browser to confirm the real sign-in and the app’s role. AACLI simulates attribute resolution, while the app applies its own access rules.

    Check. The resolver output contains the intended attributes for the exact app. The browser session separately confirms the effective role.

  4. VMware

    On a test vCenter Server, open the vSphere Client as a disposable domain user and check the intended vCenter role. In a separate session, verify the administrator in the vCenter local domain can open the client. Broadcom documents that local route for recovery if the external provider returns an error or loops.

    Check. Record the role shown for the domain user and verify the local-domain administrator can open the client independently.

  5. LastPass

    Use a new LastPass Business test user with an empty vault and a supported browser with the LastPass extension. Complete provider activation and check that the correct empty test vault opens. Follow LastPass’s separate conversion instructions before testing with any existing user.

    Check. The extension opens the empty vault owned by the newly activated test account.

  6. Verify the app outcome

    Check the visible test account and its role from inside the destination. Record any redirect error or unexpected default role and confirm the separate administrator still has access before widening the rollout.

    Check. Keep the destination account and role you observed, and verify the administrator can still get in through the separate path.

Check your result

The selected account opens the expected destination with the intended role, and the separate administrator path still works.

How to verify your setup

If you get stuck

The provider succeeds but the app denies access

Compare the provider’s app mapping with the account and role actually assigned at the destination. Confirm the browser or extension is supported. Use the recorded administrator route to restore the previous test setting if needed.

Report a problem with this guide

Explore all setup guides →