Skip to content
IT Canvass
Menu
ServiceNow
SailPoint
SAP
TutorialsContact
Examples · Lesson

Connector examples

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 attribute

Entitlement attributes

Tell the connector which multi-valued attributes are entitlements to govern:

schema.entitlementAttribute = "memberOf"   # treat group membership as an entitlement

Guidance

  • 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.

Want to learn this properly?

Our live, instructor-led SailPoint Training covers this hands-on, with real projects and a certification path.

See the courseAsk a question

Check your understanding

  1. What do connector examples show?

    • A. To translate a target's native fields into SailPoint attributes.
    • B. A chosen identity attribute like employeeId.
    • C. Schema mapping, correlation and provisioning configuration patterns.
    Show answer

    C. Schema mapping, correlation and provisioning configuration patterns.

    Schema mapping, correlation and provisioning configuration patterns.

  2. Why map the schema?

    • A. To translate a target's native fields into SailPoint attributes.
    • B. Schema mapping, correlation and provisioning configuration patterns.
    • C. A chosen identity attribute like employeeId.
    Show answer

    A. To translate a target's native fields into SailPoint attributes.

    To translate a target's native fields into SailPoint attributes.

  3. What drives correlation?

    • A. Schema mapping, correlation and provisioning configuration patterns.
    • B. A chosen identity attribute like employeeId.
    • C. To translate a target's native fields into SailPoint attributes.
    Show answer

    B. A chosen identity attribute like employeeId.

    A chosen identity attribute like employeeId.

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.
CallWhatsAppEnquire