Employee Identity (EIAM)
Add User
Identity Synchronization
# Request Specification
| Parameter | Fill-in Reference |
|---|---|
| Request URL | https://{app_domain}/callback |
| Request Method | POST |
| Request Header | Authorization: Bearer {access_token} |
# Request Parameters
| Parameter Name | Required | Type | Description |
|---|---|---|---|
| username | Yes | String(100) | Username |
| name | No | String(40) | User's Full Name |
| organizationId | Yes | String(50) | Primary Organization ID; Special case: Do not pass this parameter if the application organization model is not enabled or if the user has no affiliated organization. |
| organizationIds | Yes | Array | List of Organization IDs, supports up to 9 affiliated departments; The first one is the primary organization ID; Special case: Do not pass this parameter if the application organization model is not enabled or if the user has no affiliated organization. |
| disabled | Yes | Boolean | Whether disabled, true indicates disabled status, false indicates enabled (not disabled) |
| attrManagerId | No | String(50) | Direct Manager |
| extAttr (Custom Extended Attributes) | No | - Integer - Boolean - String - Array | ① Extended Attributes: The parameter name is defined by the attribute name defined in IDaaS Enterprise Center, Application -> Object Model -> Application Account Model -> Attributes; Enterprises can customize extended attribute names and types; ② Extended Attribute Types: Currently only supports: Number, Text, Switch, Multi-value Text |
# Response Parameters
| Parameter Name | Type | Description |
|---|---|---|
| id | String(50) | The user ID generated after the enterprise application creates the user. |
# Request Example
- Request Example with Message Signature and Encryption Enabled
{
"nonce": "AmgjjEAJbrMzWmUw",
"timestamp": 15093849585,
"eventType": "CREATE_USER",
"data": "6lu6gxrdJIXEWxQhUa3UqsXHWsDZ5LTAo/xU3zhjq9H3syCuFYDYKg==",
"signature": "K08yDiTEc094KoccOY+VYLQFxxQ="
}
1
2
3
4
5
6
7
2
3
4
5
6
7
- Decrypted JSON String Format of the Request Body
data
{
"username": "zhangsan",
"name": "张三",
"organizationId": "391551e8-160f-4993-8177-e7b9c5f6b28c",
"organizationIds": ["391551e8-160f-4993-8177-e7b9c5f6b28c","461551e8-160f-4993-8177-e7b9c5f6b212"],
"disabled":false,
"number":123456,
"switch":false,
"text":"扩展属性单值文本的值",
"multivaluedText":["扩展属性多值文本的值1","扩展属性多值文本的值2"]
}
1
2
3
4
5
6
7
8
9
10
11
2
3
4
5
6
7
8
9
10
11
- Supplementary Description for Extended Attributes: A mapping must be configured in IDaaS Enterprise Center, Resources -> Applications -> Object Model -> Application Account Model -> Mapping Definition for the downstream application to receive the defined extended attribute values and attribute information; For how to configure extended attributes and mapping definitions, please refer to: Preparation Work.
# Response Example
Status Code: 200
Request Successful
- Example response with message signature and encryption enabled
{
"code": "200",
"message": "success",
"data": "P+rXpWetRg7IP0vdhVgkVwSoZBJeQwY2zhROsJq/HJ+q6tp1qhl9L1+c"
}
1
2
3
4
5
2
3
4
5
- JSON string format of the decrypted response body
data
{
"id": "c3a26dd3-27a0-4dec-a2ac-ce211e105f97"
}
1
2
3
2
3
