Authorization
Authorization
RequiredBearer <token>< Project ID >:< Access Key > as bearer
In: header
Path Parameters
userId
RequiredstringQuery Parameters
displayName
stringThe following values are manipulated by the marshaler in httpgateway/marshaler.go in case of changing or adding new ones, need to edit the marshaler as well
active
booleanname.givenName
stringname.familyName
stringname.middleName
stringuserName
stringOK
Update SCIM User PUT
### Update an existing SCIM user, using a valid access key. This endpoint allows administrators to update an existing SCIM user. Through this API endpoint, administrators can update the displayName, phoneNumbers, emails, and if the user is active. The response includes the user's object, which includes details about the users including their email, phone, username, name, etc. It is important to note the bearer token for SCIM API endpoints. The format is `ProjectId:AccessKey` the access key must be associated with the applicable tenant and associated with the tenant admin role. ### See also - See [SCIM Management](/scim) for further details on managing SCIM provisioning. ### Endpoint Authentication Use authorization bearer header with the following format: `Authorization: Bearer <ProjectId:AccessKey>`
Load SCIM Resource Types GET
### Load SCIM resource types, using a valid access key. This API endpoint allows administrators to load the resource types available within the SCIM provisioning. The response includes an array of the available resource types. It is important to note the bearer token for SCIM API endpoints. The format is `ProjectId:AccessKey` the access key must be associated with the applicable tenant and associated with the tenant admin role. ### See also - See [SCIM Management](/scim) for further details on managing SCIM provisioning. ### Endpoint Authentication Use authorization bearer header with the following format: `Authorization: Bearer <ProjectId:AccessKey>`