Duplicate Admin Task Names Impact on Identity Manager and Identity Portal
search cancel

Duplicate Admin Task Names Impact on Identity Manager and Identity Portal

book

Article ID: 126416

calendar_today

Updated On:

Products

CA Identity Manager CA Identity Governance CA Identity Portal CA Identity Suite

Issue/Introduction

In Identity Manager and Identity Portal environments, maintaining unique names for all "admin tasks" is critical. While the system may technically allow identical names for tasks assigned to different components, non-unique naming conventions frequently cause execution errors and role synchronization issues.

Environment

CA Identity Manager 14.5
CA Identity Portal 14.5
CA Identity Suite 14.5

Cause

Several background code processes within the Identity Suite utilize task names as unique identifiers rather than internal IDs. When duplicate names exist, these calls may fail to resolve the correct task, resulting in erroneous behaviors such as:

  • Roles missing assigned tasks.
  • Inconsistent visibility of tasks within the Identity Portal.
  • Failure of "Hide in Menus" logic or tag-based filtering.

Resolution

To ensure system stability and predictable behavior, follow these naming best practices:

  1. Enforce Uniqueness: Ensure every Admin Task has a unique name across the entire Identity Suite (Manager, Portal, and Governance).
  2. Naming Convention: Implement a naming prefix or suffix to distinguish between similar tasks intended for different interfaces (e.g., [Portal] Reset Password vs [IM] Reset Password).
  3. Audit Existing Tasks: Review current task lists for name collisions if roles appear to be missing tasks or if menu visibility settings are not behaving as expected.