Configuring and Testing Attribute Sync
Key Takeaways
Attribute Sync copies mapped identity data to existing correlated source accounts.
An eligible account field appears in Create Account and maps directly from an identity attribute there.
Attribute Sync can affect every correlated account for an identity on a source and propagate a mapped null.
Use single-identity synchronization for a bounded verification and check the native field values.
Verify the full data path
Attribute synchronization uses identity data in SailPoint to keep selected external account attributes aligned. The identity profile must map the identity attribute. In the target source’s Create Account definition, the account attribute must be present and mapped directly from that identity attribute. Then select Sync with Identity for that field under the source’s Attribute Sync settings. The source must support the intended write and respond under the chosen credentials. An absent or uncorrelated account is outside the set of accounts this feature updates.
In the data flow, a human resources change can enter through aggregation and update an identity field. SailPoint can then write the field to correlated accounts on a downstream source. Conversely, when target aggregation detects a native account change to a synchronized field, SailPoint can restore the current identity field value. A newly created account can also have Attribute Sync enforced after another process creates it. Decide which field the identity model should govern before enabling the setting.
| Observed input | Expected Sync scope |
|---|---|
| Identity profile has a mapped value and one correlated source account | Eligible selected field can be written to that account |
| Same identity has two correlated accounts on the source | Sync applies to both correlated accounts |
| A different account on the same source has no identity correlation | Excluded until it is correlated to an identity |
| Target account is absent | No creation by Attribute Sync |
| Identity profile maps the synchronized value to null | Sync propagates null. Check target support and business intent |
| Account field uses only a static Create Account mapping | Change the field to the required direct identity mapping if ongoing sync is intended |
Work a department change
An employee moves from Purchasing to Finance. The authoritative source updates the mapped Department identity attribute. On a write-enabled target, department appears in Create Account with a direct Department mapping and Sync with Identity is enabled. If the employee has two correlated accounts on the target, both are in scope. A third uncorrelated account with a similar login remains outside the change. Check actual account IDs and field values after the operation. This applies differently from an access profile’s multiple-account selection, which targets a qualifying account for an automated grant.
Now suppose the incoming department unexpectedly becomes null. The documentation says a null set by the identity profile mapping is propagated, and null fields are counted as unsynchronized. Inspect missing source data deliberately. Where a blank would be unsafe, decide with the data owner what output the mapping should produce before enabling writes. Correct inconsistent values in rules or target-side normalization that would keep the systems from converging.
Handle manager data and verify recovery
The built-in Manager identity attribute is available for Create Account, but Attribute Sync uses a custom identity attribute for this case. For example, map a custom field to the needed manager value, use it as the direct Create Account mapping and configure it in Attribute Sync. Verify the connector’s required representation, such as a directory DN where applicable, and test an absent manager. The employee-to-manager relationship and the content written to the target are distinct checks.
To test a bounded change, choose Synchronize Attributes for a single identity in the Identities list. Review sync events and the exact target field. Check the identity state before assuming a scheduled sync. Active and Inactive (short-term) identities can be in scope of automatic synchronization. SailPoint documents a final sync upon transition to Inactive (long-term) and an option for an administrator to synchronize an individual identity after that. For source-wide first application, the Sync button is available on a healthy source and the full sync is limited to three runs per source in 24 hours. Ongoing eligible changes can be enforced per account. For an Attribute Sync failure, SailPoint documents requeuing and up to ten retries. After correcting the failure, you can explicitly synchronize the affected identity or perform an appropriate supported bulk sync. Check actual results, including existing profiles whose mapping expectations differ.
See SailPoint’s attribute sync prerequisites, triggers, and limits, Create Account configuration, identity state processing rules, and lifecycle identity-state configuration.
An eligible employee has two existing correlated accounts and no other accounts on a write-enabled source. Department sync is configured. Which accounts are in scope when the mapped Department changes?
Only the first account returned by the connector
Only the account selected by access profile criteria
Both correlated accounts on the source
Neither account until a new role creates a replacement account
An administrator wants to synchronize a manager value to a supported target field, using an appropriate target format. Which source and profile setup supports this?
Map the built-in Manager field directly in Attribute Sync and rely on the target to convert it
Copy an employee login into the entitlement schema
Enable account deletion to recalculate the manager at creation
Map a suitable custom identity manager field, use it directly in Create Account, and select the resulting account field for sync
Sections you finish are checked off in the contents.