Examples · LessonBy Neelima, SailPoint Architect · Published · IdentityIQ 8.4 · all levels
Connector examples
Configuration examples for common connectors.
Quick answer
These examples show connector configuration patterns, schema mapping and correlation, for typical target systems.
Key takeaways
- Schema mapping snippets
- Correlation configuration
- Provisioning operation setup
- Adapt to your target
Connector configuration maps a target system schema to SailPoint and defines correlation and provisioning behaviour. These examples illustrate the configuration patterns conceptually.
Schema mapping
Decide which native attributes are the account identity, the display name, and the correlation key:
account.identityAttribute = "distinguishedName" # unique per account
account.displayAttribute = "displayName"
correlation.key = "employeeId" # matches identity attributeEntitlement attributes
Tell the connector which multi-valued attributes are entitlements to govern:
schema.entitlementAttribute = "memberOf" # treat group membership as an entitlementGuidance
- Pick a stable correlation key that does not change.
- Test correlation on a sample before full aggregation.
- Confirm entitlement attributes aggregate as expected.
Common pitfalls
- Correlating on a mutable attribute.
- Missing entitlement mapping, so access is not governed.
- Schema drift not reflected in the mapping.
Practice challenge
+0 XPStreak ×0
Question 1 of 3
What do connector examples show?
Frequently asked questions
What does the term Connector examples refer to in SailPoint?
Connector configuration maps a target system schema to SailPoint and defines correlation and provisioning behaviour. These examples illustrate the configuration patterns conceptually.
What is worth remembering about Connector examples in practice?
Pick a stable correlation key that does not change. Test correlation on a sample before full aggregation. Confirm entitlement attributes aggregate as expected.
What tends to go wrong with Connector examples?
Correlating on a mutable attribute. Missing entitlement mapping, so access is not governed. Schema drift not reflected in the mapping.
Want this with a live instructor and a lab tenant?