Overview:
Identity Security Cloud uses Identity Profile priority to determine which Identity Profile is associated with an identity when the same user has accounts in multiple authoritative sources. A lower priority number represents a higher priority.
Identity Profile priority is assigned automatically when an Identity Profile is created. By default, the first Identity Profile is assigned a priority of 10, the next 20, and so on. The priority can be changed to other numeric values as needed; it does not have to be a multiple of 10. Each Identity profile should have a unique priority value.
This article demonstrates a simple test using one identity, 843723, with two accounts from an Employee source and a Contractor source. The Identity Profile priority is updated using both Postman and the SailPoint ISC extension for VS Code.
Prerequisites:
- Two authoritative sources with their corresponding Identity Profiles configured.
- At least one common identity present in both authoritative sources.
- Postman configured to access your SailPoint Identity Security Cloud tenant.
- Visual Studio Code with the SailPoint ISC extension configured to access your SailPoint Identity Security Cloud tenant
Setup:
Two authoritative sources were loaded from CSV files. Both files contain the same user, 843723, while the employeeType and costCenter values differ.
Employee Profile:
| userName | firstName | lastName | displayName | department | title | managerEmployeeNumber | location | employeeType | costCenter | |
|---|---|---|---|---|---|---|---|---|---|---|
| 843723 | Ravi | Krishna | Ravi Krishna | ravi.krishna@demo.com | Engineering | Software Engineer | 324533 | Chicago | Employee | ENG500 |
Contractor Profile:
| userName | firstName | lastName | displayName | department | title | managerEmployeeNumber | location | employeeType | costCenter | |
|---|---|---|---|---|---|---|---|---|---|---|
| 843723 | Ravi | Krishna | Ravi Krishna | ravi.krishna@demo.com | Engineering | Software Engineer | 324533 | Chicago | Contractor | ENG600 |
The only differences between the two records are:
| Field | Employee Profile | Contractor Profile |
|---|---|---|
employeeType |
Employee | Contractor |
costCenter |
ENG500 | ENG600 |
Each source has its own Identity Profile. In this test, the Employee Profile starts at priority 720 and the Contractor Profile at 710.
Before the priority change:
With Contractor Profile at 710 and Employee Profile at 720, identity 843723 was associated with the Contractor Profile. The identity shows cost center ENG600 and worker type Contractor, matching the Contractor source.
Update priority with Postman:
The SailPoint Identity Profiles API can be used to read and update an Identity Profile. In the Postman collection used for this test, the request path is {{baseUrl}}/identity-profiles/v1/:identity-profile-id.
1. Get the current priority:
Run Get identity profile with the Identity Profile ID in the identity-profile-id path variable. The request returned 200 OK and showed the Employee Profile priority as 720.
2. Change the priority:
Run Update identity profile (PATCH) using the same URL. Use Content-Type: application/json-patch+json and set the request body to raw JSON:
[
{
"op": "add",
"path": "/priority",
"value": 705
}
]
The request returned 200 OK and the response showed priority 705.
After the update, the Employee Profile showed priority 705 and status Needs Processing in the ISC UI. Apply the pending changes before validating the identity.
3. Verify the identity:
After the Employee Profile was processed, it had priority 705 compared with the Contractor Profile at 710. Identity 843723 was then associated with the Employee Profile, and its attributes showed cost center ENG500 and worker type Employee.
Update priority with the VS Code extension:
The Identity Profile priority can also be updated using the SailPoint ISC extension for VS Code. Open the required Contractor Profile from the Identity profiles folder, edit the priority value, and save the change with Ctrl+S. The updated value is then reflected in the ISC UI.
This demonstrates that the priority can also be modified directly from the VS Code ISC extension.
Before the change:
After the change:
After the VS Code update, the ISC UI showed the Contractor Profile with priority 725, confirming that the Identity Profile priority was successfully updated using the VS Code ISC extension.
