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 i 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 |
|---|---|
| USRPRF | Account |
| USRPRF | Group |
Default Account Attributes
The IBM i connector supports the following default account schema attributes and customer configurable attributes. The attributes must be defined as strings if not specified.
The following lists the account and account - group attributes:
| Attribute Name | Description |
|---|---|
| USRPRF | User profile. |
| PWDEXP | Set password to expired. |
| STATUS | Current user status. |
| USRCLS | User class. |
| ASTLVL | Assistance level. |
| CURLIB | Current library. |
| INLPGM | Initial program to call. |
| INLMNU | Initial menu. |
| LMTCPB | Limit capabilities. |
| TEXT | Text description. |
| SPCAUT | Special authority. |
| SPCENV | Special environment. |
| DSPSGNINF | Display sign-on information. |
| PWDEXPITV | Password expiration interval. |
| LCLPWDMGT | Local password management. |
| LMTDEVSSN | Limit device sessions. |
| KBDBUF | Keyboard buffering. |
| MAXSTG | Maximum allowed storage. |
| PTYLMT | Highest schedule priority. |
| JOBD | Job description. |
| GRPPRF | Group profile. |
| OWNER | Owner. |
| GRPAUT | Group authority. |
| GRPAUTTYP | Group authority type. |
| SUPGRPPRF | Supplemental groups. |
| ACGCDE | Accounting code. |
| OBJAUD | Object Auditing. |
| MSGQ | Message queue. |
| DLVRY | Delivery. |
| SEV | Severity code filter. |
| PRTDEV | Print device. |
| OUTQ | Output queue. |
| ATNPGM | Attention program. |
| SRTSEQ | Sort sequence. |
| LANGID | Language ID. |
| CNTRYID | Country or Region ID. |
| CCSID | Coded character set ID. |
| CHRIDCTL | Character Identifier control. |
| SETOBJATTR | Local job attributes. |
| LOCALE | Locale. |
| USROPT | User options. |
| UID | User ID number. |
| GID | Group ID number (Only for Groups). |
| HOMEDIR | Home directory. |
| AUDLVL | Audit Level. |
| AUTL | Authorization Lists |
| PWDLASTCHG | Date and time when the sign on password was changed. |
| PREVSIGNON | Date and time of previous sign on. |
| PWDEXPDATE | Date when password will expire. |
| INVSIGNON | Number of unsuccessful sign on attempts. |
| USREXPACT | User Expiration Action. |
| USREXPDATE | User Expiration Date. |
| USREXPITV | User Expiration Interval. |
| LSTUSEDATE | Last Used Date. |
| CHGDATE | Date and time of the last change to the user profile. |
| CTRBYUSER | Created by user. |
Note
The PREVSIGNON attribute value will now align with day light saving time settings.
Include Permissions in Account Schema
When permissions are aggregated (For example, when includePermissions="true" is set to true in the account schema definition and the privilege attribute is included in the account schema), the permissions are aggregated under the directPermissions attribute, not the privilege attribute itself. This data is not visible in the UI but is included in the link or identity XML/JSON.
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.