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 Splunk On-Call 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 |
|---|---|
| username | Account |
Default Account Attributes
The Splunk On-Call connector supports the following default account schema attributes and customer configurable attributes. The attributes must be defined as strings if not specified.
| Account ID | Schema Object Type |
|---|---|
| firstName | First name of the employee |
| lastName | Last name of the employee |
| creationAt | Employee account creation date |
| passwordLastUpdated | Timestamp when the user's password was last updated |
| Email address of the user | |
| verified | User account verification status |
| selfUrl | URL to the user's profile in the API |
| username | Unique username identifier for the user |
| teamId | Current user's Team ID |
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 Teams Attributes
| Team Object | Description |
|---|---|
| teamId | Unique identifier (slug) for the team |
| name | Display name of the team |
| _selfUrl | API endpoint to get detailed team info |
| _adminsUrl | API endpoint to retrieve or manage team admins |
| _policiesUrl | API endpoint to manage or view team policies |
| _membersUrl | API endpoint to retrieve team members |
| version | Internal version counter |
| memberCount | Team member count |
| isDefaultTeam | User's default team |
| description | Team description |