2.3 Identity Profiles and Attribute Mapping
Key Takeaways
Each identity profile requires mappings that populate User Name (
uid), Work Email (email) and Last Name (lastname).The
uidvalue must be unique across identity profiles. Missing required values or a duplicateuidcan raise an identity exception.A profile can map attributes from its authoritative source and from other appropriate account sources.
Preview mappings with representative identities, then apply the supported processing action to put profile changes into effect.
Start with which values a profile must provide
An identity profile determines how identities based on an authoritative source are populated and sets other behavior such as security settings. A mapping connects an identity attribute to its input. A transform can normalize or derive a value when copying the input directly is insufficient. For employee and non-employee populations, confirm the inputs separately because the two sources may give the same information different field names.
| Required identity attribute | Employee example | Contractor example |
|---|---|---|
User Name (uid) | Stable employee login identifier | Stable contractor login identifier that will be unique in the same tenant |
Work Email (email) | Work address from a correlated directory account, if it will be present when needed | Work address maintained in the contractor source |
Last Name (lastname) | Family name supplied by the HR system | Family name supplied by the contractor source |
SailPoint requires mappings for all three and non-null values for the resulting identity attributes. The user name must be unique across the tenant’s identities, including identities in other profiles. The work email value must be present even though SailPoint does not validate that the value is an email address at this mapping stage. Real operational requirements may also depend on usable email values. A placeholder value might avoid a null in a lab while leaving notification routing incorrect. Check both requirements when designing the mapping.
Decide how to map each attribute
Map direct values when a reliable source already provides them. For instance, map the employee source’s family name to lastname. A supported concatenation transform can build a display name from first and last names. A supported lowercase transform can standardize case when policy calls for that output. Those transforms solve particular data problems and are optional when the existing data is already suitable. They neither redefine which identity owns an account nor make an absent source value exist.
An identity profile can pull one value from the primary HR source and another from a correlated directory account. Account availability matters. Consider an employee who is loaded from HR three days before their directory account exists. If the only input for their required work email comes from that directory, check what the mapping produces for a prehire. A valid design needs an approved source value available at that stage or a controlled onboarding sequence. Creating the directory account after a null-value exception does not by itself prove all the intended mapping inputs were later processed. Verify the identity after the data and processing are complete.
Native non-employee sources have defaults for user name and display name linked to the unique account name. SailPoint’s documentation directs the engineer to map the other required values as well. Check the resulting mappings for work email and last name even if the initial setup screens already list a profile.
Preview, apply, and verify
- In the profile’s Mappings view, choose the source and its account attribute for each required value. Add a transform only where the desired output requires it.
- Review the pending mappings and use Preview with representative identities, including one from each population where data differs and cases with incomplete or unusual source values. Confirm required output and expected optional values.
- Save any adjustments and apply changes for identities that need processing. Confirm the identity’s current values and any related processing or exception status.
- If an authoritative account lacks a required value or duplicates another
uid, use the identity exception evidence to find and correct the affected input, then reaggregate as appropriate.
Worked example. Two unrelated records have an employee or contractor login value rlee. Both also have a non-null work email and last name. The required attributes may be mapped in both profiles, yet the duplicated user name conflicts with tenant-wide uniqueness. Obtain a stable unique identifier through the organization’s identity naming rule. Preview the mapping and confirm that the exception clears in the appropriate processed result. Changing the display name would leave both user names identical.
See SailPoint’s identity profile mappings and exceptions, non-employee source defaults, identity processing, and transform operations.
An employee profile and a contractor profile each map an account for a different person. Both mappings would produce uid rlee. Both email and last name are populated. Which issue remains?
User Name must be unique across the two profiles
Identity profiles always require each user’s manager first
Both profiles must have identical work email values
The work email field must be dropped if user names collide
A native non-employee source supplies default identity mappings for user name and display name. Which additional mapping values must the engineer confirm for the minimum required set?
Title and manager
Department and telephone
Work email and last name
First name and cost center
Sections you finish are checked off in the contents.