Access History does not properly display entitlement name

Feedback General Feedback
,
1

Hi all :slight_smile:

We observe access history containing entitlements being added that sometimes refer to the entitlement id instead of the name. This makes it difficult to:

  1. See the record and figure out which access item corresponds to it.
  2. Filter for records based on entitlement name. Some results are not visible if this issue occurs.

We notice this issue occurs when the following steps occur in this order, both on a new source, and on a source that is being used for a while already.

  1. Entitlement is created natively and assigned to some accounts.
  2. Account aggregation is performed, entitlement assignment is detected and administrated in access history, search, and on account. Only entitlement ID is known now.
  3. Entitlement aggregation is performed, entitlement corresponding to this ID is found and account data in UI is updated to display the entitlement name. Also identity search object is updated to properly refer to the entitlement. But Access history objects are not updated to now properly refer to the right entitlement name.

This data inconsistency issue makes working with access history more difficult.

2

Hi, were you able to resolve this issue? Both our Oracle Fusion Cloud and Entra applications are useless in access history as the name of the entitlement is a long GUID. I need the column in access history to be the display name of the entitlement.

3

Hi @jackb032,

This is not something we can fix ourselves. We need SailPoint to fix this issue since their code is causing it, but I have seen no progress being made on this topic. Please report this to your CSM and link to this post. Perhaps it will gain traction that way.