Change of Identity Profile for Identity with 2 auth sources

Identity Security Cloud (ISC) ISC Discussion and Questions
1

I’m experiencing issues with changing identity profiles for users.

For Example, the user mrossi is in the HR_FromFile autoritative source.
I execute the aggragtion and the identity mrossi is created linked to the identity profile HR_FromFile.

We have a second autoritative source called HR_fromWorkday with the same schema of the HR_FromFile and same data.
When I aggregate the second source HR_fromWorkday, mrossi remains on the HR_FromFile identity profile and doesn’t change to HR_fromWorkday.

If I open the Identity mrossi I can see linked the 2 account HR_FromFile and HR_fromWorkday with same username so the correlation rule is correct.

The only way to make it work is to delete the account from the HR_FromFile source and run an aggregation. In this way the identity profile switch from HR_FromFile to HR_fromWorkday.

I don’t undestand this behavior.
I was tested in my lab the same scenario with sourceFromFile1 and sourceFromFile2. An identity created with sourceFromFile1 has changed the identity profile when has been aggregated from sourceFromFile2.

Is there a way to force the change of identity profile ?

Thanks

2

Hi @ffalcitelli ,
Identities will be associated with the highest priority identity profile where they have an account on its authoritative source.

By default, identity profiles are prioritized based on the order they were created. The earlier an identity profile is created, the higher priority it is assigned.

If you need to change this order, you can use the Update Identity Profile API to change the identity profiles’ priority attribute values.

3

Perfect. Is working:

STEPS TO DO:

  1. GET https://myclient-sb.api.identitynow.com/v3/identity-profiles/ed468c9f16494da6a8b05beb2fb0cff3 and read the actual priority
  2. PATCH https://myclient-sb.api.identitynow.com/v3/identity-profiles/869acac61f5646e6b258cae4a48867fd with Header Content-Type=application/json-patch+json and body:
[
    {
        "op": "replace",
        "path": "/priority",
        "value": "19"
    }
]

The value must be unique and not used in any other identity profile.
Priority 1 is the highest.