Policy XPress Account Search Failures Due to Case Sensitivity Mismatch

Products

• CA Identity Suite
• CA Identity Manager

Issue/Introduction

This article provides instructions for troubleshooting and resolving issues where Policy XPress (PX) policies fail to detect user accounts or return a "No Account Found" error during attribute correlation or endpoint detection.

Environment

Identity Manager 14.x

Cause

Policy XPress (PX) correlation searches require strict case consistency for account names. Identity Manager only supports account searches when the input name is provided in either all lower-case or all upper-case letters. The search will fail if the provided account name contains a mix of upper and lower-case characters.

• PX policies configured to correlate attributes (e.g., HR data flows to Active Directory) fail to link successfully.
• The system logs or UI displays the error message: "No Account Found."
• This error persists despite the user account being present and correctly linked in Identity Manager.

Resolution

To resolve this issue, you must normalize the account names used in your PX policy configuration to ensure they match the format stored in your endpoint.

1. Review PX Policy Configuration: Inspect the PX policy definition and verify the account name format being passed to the search function.

2. Normalize Account Names: Ensure all account names are converted to a consistent case format:

   • Option A: Convert all account names to lower-case.
   • Option B: Convert all account names to upper-case.

3. Validate Changes:

   • Save the updated PX policy.
   • Retrigger the correlation task to ensure the system successfully detects the endpoint account.