Extending Core SCIM Group
The SCIM core objects can be extended by attaching several objects and declaring these in the object schema. This section details which objects can be attached to the Group object.
The API version supported by HID Authentication Service is
Previous versions of the API are also supported with the corresponding functionality.
urn:hid:scim:api:idp:2.0:GroupParent
Optionally attached to Group, the parent group code is displayed.
Verb usage: GET(read), PUT(replace), POST(create)
Group – an entity of type urn:hid:scim:api:idp:2.0:GroupParent:
-
type – the type of attribute from (STRING). Only returned.
-
display – the type of attribute from (STRING). Only returned.
-
value – the value of the attribute. Required for all calls.
-
$ref – url to find the Group. Only returned.
Example
"urn:hid:scim:api:idp:2.0:GroupParent": {
"parent": {
"type": "Group",
"display": "Customers User Type",
"value": "UT_CUST"
"$ref": "https://[base-server-url]/SCIM/tenant/v2/Groups/UT_CUST"
}}
}
To create a group, it is mandatory to include this entity in the request, as it is only possible to create a group under an existing parent group.
urn:hid:scim:api:idp:2.0:userattribute:Type
Optionally, attached to Group, the list of user attribute types for the group that can be updated.
"userAttributeTypes": [
{
"schemas": ["urn:hid:scim:api:idp:2.0:userattribute:Type"],
"id": "ADDRESS1",
"meta": {
"resourceType": "UserAttributeType",
"location": "https://[base-server-url]/scim/tenant/v2/User/AttributeType/ADDRESS1",
"version": "1"
},
"name": "Address Line 1"
}
]