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 Rebilly 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 Rebilly 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 identifier for the Rebilly user |
| Email address of the user | |
| firstName | First name of the user |
| lastName | Last name of the user |
| businessPhone | Business phone number of the user |
| allowedIps | List of IP addresses permitted to access the user account |
| createdTime | Timestamp when the user account was created |
| updatedTime | Timestamp when the user account was last updated |
| loginTime | Date and time when the user last logged in |
| status | Current status of the user account |
| country | Country of the user |
| availableCurrencies | Array of reporting currencies enabled for the merchant |
| reportingCurrency | User’s currency code in ISO 4217 format |
| roleIds | Role IDs associated with the user (entitlement mapping to group/role) |
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 Role Attributes
The Rebilly connector supports roles. The following attributes must be configured on the managed system and in the SailPoint source schema to manage roles.
| Attribute Name | Description |
|---|---|
| id | Unique identifier of the role |
| name | Name of the user role |
| description | Description of the role |
| organizationId | Identifier of the organization(s) where the role is assigned |
| permissions | Individual permissions associated with the role |
| createdTime | Date and time when the role was created |
| updatedTime | Date and time when the role was updated |
| usersCount | Number of users assigned to this role |
| allowedIps | List of IP addresses permitted for accounts with this role |