The user
JSON object
The following attributes are available in the user
JSON
object.
“scim-outline”
- Provides the starting point for constructing a new Verify-SCIM directory
user
object in JSON format. Each attribute from the LDAP AD entry is processed and added to this object. “ldap-object-class”
- Provides the LDAP AD object class value that is used to detect User LDAP AD entries.
“scim-external-id-attr”
- Provides the name of the Verify-SCIM directory attribute
in which to store the LDAP AD entry unique value. This unique value is used to connect the LDAP AD
entry to the Verify-SCIM
directory entry. Typically
“externalId”
is used. "ldap-to-scim"
- Is an array that defines how to map relevant Active Directory attributes to Cloud Directory
attributes when you create or modify users. Each entry in the array defines how to map one Active Directory attribute and consists of:
"ldap"
- The name of the Active Directory attribute to map from.
"tweaks"
- An optional set of attribute value modification methods to apply to the Active Directory attribute value.
"new-attr"
- Specifies how to format the Active Directory
value into a Cloud Directory attribute that is added to the
“scim-outline”
when a user is created. "mod-attr"
- Specifies how to format the Active Directory value into a Cloud Directory attribute modification request.
"is-dn"
- Indicates that the value of the attribute is a distinguished name (DN) that refers to another
user or group that must be mapped to a Verify user or group before it is
set in the Cloud Directory. Two examples of this type of attribute are
group members
and auser’s manager
. "is-multi-value"
- This attribute is supported for the group member attribute and custom attribute. When set, all LDAP values for the attribute are applied to the Cloud Directory. If not set, the attributes are considered to be single-value, and only one value is used even if multiple values exist.
"is-binary"
- This attribute defaults to false. Set it to true if the attribute from Active Directory is binary that is, it contains
non-text values. An example is the
ObjectGUID
attribute. Binary attributes are base 64-encoded before they are applied to the Cloud Directory attribute.