Modify User

Request Specification {/examples/}

Parameter	Reference
Request URL	https://{app_domain}/callback
Request Method	POST
Request Header	Authorization: Bearer {access_token}

Request Parameters {/examples/}

Parameter Name	Required	Type	Description
id	Yes	String(50)	Enterprise Application User ID
username	Yes	String(100)	Username. The username is unique and cannot be duplicated.
disabled	No	Boolean	Whether disabled. true indicates disabled status, false indicates enabled (not disabled).
name	No	String(40)	User's full name
organizationId	Yes	String(50)	Primary organization unit ID. Special case: Do not pass this parameter if the application organization model is not enabled or the user has no associated organization.
organizationIds	Yes	Array	List of organization unit IDs, supporting up to 9 affiliated departments. The first position is the primary organization unit ID. Special case: Do not pass this parameter if the application organization model is not enabled or the user has no associated organizations.
attrManagerId	No	String(50)	Direct superior (manager)
extAttr (Custom Extended Attributes)	No	- Integer - Boolean - String - Array	① Extended Attribute: The parameter name is defined by the attribute name defined in IDaaS Enterprise Center, under 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)	User ID of the enterprise application

Request Example

• Request example with message signature and encryption enabled

{
	"nonce": "AmgjjEAJbrMzWmUw",
	"timestamp": 15093849585,
	"eventType": "UPDATE_USER",
	"data": "6lu6gxrHydJIXEQhUa3UqsXHWsDZ5LTAo/xU3zhjq9H3syCuFYDYKg==",
	"signature": "K08yDiTEc094KoccOY+VYLQFxxQ="
}

• JSON string format of the request body data after decryption

{
	"id": "c3a26dd3-27a0-4dec-a2ac-ce211e105f97",
	"username": "zhangs",
	"name": "张三2",
	"organizationId": "391551e8-160f-4993-8177-e7b9c5f6b28c",
	"organizationIds": ["391551e8-160f-4993-8177-e7b9c5f6b28c","461551e8-160f-4993-8177-e7b9c5f6b212"],
	"disabled":false,
	"number":123456,
    "switch":false,
    "text":"Value of the extended attribute single-valued text",
    "multivaluedText":["Value 1 of the extended attribute multi-valued text","Value 2 of the extended attribute multi-valued text"]
}

• Supplementary description for extended attributes: IDaaS needs to configure mappings in the Enterprise Center, under Resources -> Applications -> Object Model -> Application Account Model -> Mapping Definition. Only then can the downstream application 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

• Response example with message signature and encryption enabled

{
	"code": "200",
	"message": "success",
	"data": "P+rXpWetRg7IP0vdhVgkVwSoZBJeQwY2zhROsJq/HJ+q6tp1qhl9L1+c"
}

• JSON string format of the response body data after decryption

{
	"id": "c3a26dd3-27a0-4dec-a2ac-ce211e105f97"
}