Impact of real-time persistent cache refresh on global profile identities
The following table describes the expected outcome for global profile identities based on events detected on the source.
Source Event Detected by Connector | Result |
|---|---|
An entry that is currently correlated/linked in the global profile entry has been updated. | Applicable attributes are updated in the global profile. |
An entry that is currently marked as unresolved has been updated. | If the update results in a correlation, the entry is linked in the global profile and removed from unresolved. |
An entry that is currently correlated/linked in the global profile has been deleted. | If the entry is linked to other entries in the global profile, the attributes coming from the source the entry was deleted from are removed from the global profile. |
An entry that is currently marked as unresolved has been deleted. | The entry is removed from unresolved. |
A new entry has been added. | Correlation rules are evaluated and the entry is either linked to a matching global profile identity, created as a new identity in the global profile, or marked as unresolved and not added into the global profile. |
An entry is moved to a new container that is not below the naming context configured for the identity source, making it out of the scope of the Global Identity Builder project. For example, assume the user | If the entry is linked to other entries in the global profile, the attributes coming from the entry identified by the old DN are removed from the global profile. |
An entry is moved to a new container that is below the naming context configured for the identity source. For example, assume the user | If the entry is in the global profile, the |
An entry is moved from a container that was not in scope to a new container that is below the naming context configured for the identity source. For example, assume the user | Correlation rules are evaluated and the entry is either linked to an existing global profile identity, added as a new identity, or added to unresolved. |
Identity source logs
A log is generated for each identity source and updated after uploads or when a source event triggers the real-time persistent cache refresh. Logs are located at: {RLI_HOME}/vds_server/logs/correlation/{NAME_OF_CORRELATION_PROJECT}/{IDENTITY_SOURCE}.csv
The Status column indicates the action that was performed on each identity. The status values are: new, new(manual), moved, correlated, correlated(manual), already correlated, ignored, or error. Below is a description of each.
Status | Description |
|---|---|
| Indicates a new identity that is pushed into the global profile. |
| Indicates that the entry was manually added as a new identity in the global profile list by an administrator using the Global Identity Builder. |
| This status is not seen during uploads. It is only applicable for events related to real-time persistent cache refresh of the global profile list. For LDAP identity sources, if a capture connector detects a |
| Indicates the entry was able to match an identity in the global profile list. |
| Indicates that the entry was manually correlated to an existing identity in the global profile list by an administrator using the Global Identity Builder. |
| Indicates that the entry was already in the global profile list, and it was simply refreshed. |
| Indicates the entry was neither correlated to an existing identity in the global profile list nor created as a new identity in the global profile list. This means that the correlation rules were applied on the identity source entry and: |
| Indicates there was an error that occurred when correlating an identity. An example of a common error is one indicating that there was a disconnection to the identity data source. |
The entryDn column is the full DN of the identity source entry that was processed.
The vuid column contains the unique identifier for the entry inside the global profile.
The filter column indicates the last filter that was evaluated by the correlation engine. If an entry has status correlated, this filter is the exact filter that allowed a successful correlation. If it is N/A then the entry was already correlated, ignored or an error occurred.
The ruleNumber column indicates the correlation rule number that was used to correlate the entry. If it is N/A the entry was already correlated, ignored, or error occurred.
The time column indicates the exact date/time when the entry was processed.
For details on logs related to the real-time persistent cache refresh components (for example, connectors, sync engine, agent) please see the RadiantOne Logging and Troubleshooting Guide.
To learn more about Global Identity Builder, please read the chapter that describes how to link existing groups to global profile identities.