...
Configuration Property | Type | Required | Description | ||
---|---|---|---|---|---|
| String | X | Base address of the SCIM REST service. | ||
| String | Username for authentication to the target RESTful service | |||
| GuardedString | Password for authentication to the target RESTful service | |||
| String | X | Value for the HTTP | ||
| String | X | Value for the HTTP | ||
| String | Client id for authentication to the target RESTful service | |||
| String | Client secret for authentication to the target RESTful service | |||
| String | Field id of the JSON object node, returned from target Access Token RESTful service, that contains token value; defaults to access_token | |||
| String | Base address of the target RESTful service used to obtain access token | |||
| String | Value for the HTTP Content-Type header for the target Access Token RESTful service; defaults to application/x-www-form-urlencoded | |||
| String | SCIM Resource Schema representation in JSON format, used to specify custom attributes. See here as reference | |||
| String | Method used for updates ( |
A sample value for
The following, instead, is a sample for 2.0 version:
The important parts are:
Indeed, the resulting schema representation will use the same name convention used for other complex attributes, e.g.:
so in this case it will be:
To manage version 2.0 Enterprise User attributes just use the following attributes:
To manage version 1.1 Enterprise User attributes just use the following attributes:
|