Summary

SCIM (System for Cross-Domain Identity Management) is a standardized protocol used to manage user and group identities across both cloud and on-premise applications. The primary role of SCIM in IVIA is to expose identity data stored in the LDAP directory or IVIA's internal registry to external systems, enabling secure and efficient user and group provisioning (create), de-provisioning (delete), update, and read operations.

By default, when configuring MS Windows AD as an LDAP type in an AAC Server Connection, the “sAMAccountName” attribute does not appear in the “User DN Attribute” & “User ID Attribute” dropdowns within the LDAP Server section under the User Profile tab of the SCIM Configuration.

Here, the “sAMAccountName” attribute is important because it typically serves as the unique user identifier when integrating with Microsoft Windows Active Directory (MS AD). SCIM requires a userID attribute to map its userName field, which is a mandatory field used to uniquely identify users across create, read, update, and delete (CRUD) operations.

On the AD side, this attribute represents the user's login name (such as john.wick) and is commonly used for authN. By configuring that as the “User ID Attribute” in the SCIM, IVIA ensures that identity operations align with how users are identified and authenticated across enterprise systems. Without mapping this attribute, SCIM may not correctly identify or manage users in an Active Directory-backed identity environment.

Please, follow the steps to add the sAMAccountName attribute