Schema Reference
The application schema is used to configure the objects returned from a connector.
Note
-
The Account Schema tab is used to define the attributes for each object type in the application being configured. The schema attributes can be defined as Entitlement or Multi-Valued. Refer to Managing Source Account Schemas for more information.
-
The schema attributes that are not present by default must be defined as strings if not specified.
The Leapsome connector uses the following default correlation and object configurations.
Default Account Schema
Each source supports a variety of details, or attributes, about each user who has an account, such as their name, email address, manager name, and location.
The set of account attributes each source stores and how they're organized is known as the account's schema. To best represent your data, you can configure sources to use an account schema matching the one you use in the external connector. Refer to Managing Source Account Schemas for more information.
Default Account ID
SailPoint requires that certain attributes remain in your configuration. These attributes are referred to as account IDs.
Caution
Changing the attribute marked as the account ID after aggregating accounts can result in duplicate accounts being created. To avoid this, either reset the accounts on this source before editing the account ID attribute or edit the account ID attribute before aggregating accounts.
To resolve issues caused by changing account IDs, reconfigure them to their default values.
The following table lists the default account IDs for this connector:
| Account ID | Schema Object Type |
|---|---|
| id | Account |
Default Account Attributes
The Leapsome connector supports the following default account schema attributes and customer configurable attributes. The attributes must be defined as strings if not specified.
| Attribute Name | Description |
|---|---|
| id | Unique SCIM identifier of the user |
| userName | Login identifier of the user, as defined by the SCIM userName attribute |
| displayName | Display name of the user |
| externalId | Identifier assigned to the user by the calling SCIM client |
| active | Boolean flag indicating whether the user account is active |
| title | Job title of the user |
| familyName | Family (last) name of the user |
| givenName | Given (first) name of the user |
| Primary email address of the user, taken from the SCIM emails array entry where primary is true | |
| manager | Identifier of the user's manager, from the SCIM manager.value attribute |
| created | Timestamp when the user account was created, in ISO 8601 format |
| lastModified | Timestamp when the user account was last modified, in ISO 8601 format |
| groups | Identifiers of the groups associated with the user |
Default Entitlement Attributes
Entitlement attributes define the entitlements, such as groups or roles, that can be assigned to the managed system's user accounts. Refer to Managing Entitlements for more information.
Caution
Changing the attribute marked as the Entitlement ID after aggregating accounts or entitlements can result in duplicate entitlements being created, or access profiles and roles breaking. To avoid this, edit the entitlement schema before performing any aggregations.
Default Group Attributes
The Leapsome connector also supports groups. The following attributes must be configured on the managed system and in the SailPoint source schema to manage groups.
| Attribute Name | Description |
|---|---|
| id | Unique SCIM identifier of the group |
| displayName | Human-readable name of the group |
| externalId | Identifier assigned to the group by the calling SCIM client |
| groupId | Internal identifier of the group |
| created | Timestamp when the group was created, in ISO 8601 format |
| lastModified | Timestamp when the group was last modified, in ISO 8601 format |