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 IBM Security Verify Access 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 |
|---|---|
| userid | Account |
| GroupName | Group |
Default Account Attributes
The IBM Security Verify Access 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 |
|---|---|
| userid | The user's User ID in the managed system |
| first_name | The user's first name |
| last_name | The user's last name |
| registryUID | The account name stored in the user registry |
| description | Text description the user |
| groups | The Access Manager groups to which the user belongs |
| noPwdPolicy | Indicates if a password policy is enforced |
| ssoUser | Indicates if the user has single sign-on capabilities |
| accountValid | Indicates if the account is disabled |
| passwordvalid | Indicates if the account is having valid password |
| importFromregistry | Indicates if the new user must be imported from a registry server, not created in a registry server |
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 IBM Security Verify Access 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 |
|---|---|
| name | Name of the group |
| registryUID | The group name stored in the user registry |
| description | Text describing the Group. |
GSO Credentials
Important
GSO web and GSO group credentials aren't included in the schemas for new connector deployments of the connector for IBM Security Verify Access. They apply for connectors which rely on JAR files. You can manually add these credentials to the connector via aggregation or provisioning.
| Attribute Name | Description |
|---|---|
| gsoWebCreds | The list of GSO Web credentials assigned to a user. Displays in the following format: <gso name>:<user sign-on ID> |
| gsoGroupCreds | Shows the list of GSO group credentials assigned to a user. Displays in the following format: <gso name>:<user sign-on ID> |
Add GSO Web Credentials with Aggregation
To aggregate GSO web credentials and GSO group credentials add gsoWebCreds and gsoGroupCreds as account schema attributes.
Note
Adding GSO web credentials to the account aggregation may negatively affect the performance of account aggregation.
Add GSO Web Credentials with Provisioning
To provision these attributes, add the gsoWebCreds and gsoGroupCreds attributes to the Create Account provisioning policy.
Provide the values in the following formats:
GSO Web Credentials
| Attribute Name | Value |
|---|---|
gsoWebCreds_name_0: |
gso_name:sign-on id |
gsoWebCreds_password_0: |
gso-password |
GSO Group Credentials
| Attribute Name | Value |
|---|---|
gsoGroupCreds_name_0: |
gso_group_name:sign-on id |
gsoGroupCreds_password_0: |
gso-password |
Note
To add multiple GSO profile, provide multiple GSO attribute list as shown below:
gsoWebCreds_name_1,gsoWebCreds_name_2,gsoWebCreds_name_3...
Documentation Feedback
Feedback is provided as an informational resource only and does not form part of SailPoint’s official product documentation. SailPoint does not warrant or make any guarantees about the feedback (including without limitation as to its accuracy, relevance, or reliability). All feedback is subject to the terms set forth at https://developer.sailpoint.com/discuss/tos.