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 Alegra 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 Alegra 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 user account, used as the account identity attribute
Global ID	Global identifier for the user account
Email	Email address of the user, used as the account display attribute
Role	Security role assigned to the user, such as admin or user, aggregated as a Role entitlement
Position	Job position of the user in the organization
Username	Username for the account
First Name	First name of the user
Last Name	Last name of the user
Phone	Phone number for the user
Phone Code	Country calling code for the user phone number
Status	Current status of the user account, typical values are active and inactive
Company Name	Name of the organization associated with the user
Registry Date	Date the user was registered
UUID	Additional unique reference for the user
Has Invitation Key	Indicates whether the user still has a pending invitation to accept

Note

Id is used as the account identity attribute because Alegra retrieves an individual user with this value. Global ID and UUID are also collected, but they are not used to look up a single user. Email is the account display attribute.

Account Correlation

Accounts are correlated to identities by matching the identity email attribute to the account Email attribute.

Identity Attribute	Operation	Account Attribute
email	EQ	Email

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.

This connector aggregates Role as the entitlement type associated with accounts.

Attribute Name	Description
Role	Security role assigned to the Alegra user, such as admin or user. Aggregated with the account.

Note

Role entitlements are collected with each account during account aggregation.