Enabling Automatic Provisioning
Function
This API is used to enable automatic provisioning and automatic SCIM synchronization. It can be called only from the organization's management account or from a delegated administrator account of a cloud service.
URI
POST /v1/identity-stores/{identity_store_id}/provision-tenant
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
identity_store_id |
Yes |
String |
Globally unique ID of an identity source. |
Request Parameters
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
X-Security-Token |
No |
String |
Security token (session token) of your temporary security credentials. If a temporary security credential is used, this header is required. |
Response Parameters
Status code: 201
|
Parameter |
Type |
Description |
|---|---|---|
|
creation_time |
Number |
Creation time. |
|
scim_endpoint |
String |
SCIM endpoint. |
|
tenant_id |
String |
Globally unique ID generated after auto-provisioning is enabled. |
Status code: 400
|
Parameter |
Type |
Description |
|---|---|---|
|
error_code |
String |
Error code. |
|
error_msg |
String |
Error message. |
|
request_id |
String |
Unique ID of a request. |
Status code: 403
|
Parameter |
Type |
Description |
|---|---|---|
|
error_code |
String |
Error code. |
|
error_msg |
String |
Error message. |
|
request_id |
String |
Unique ID of a request. |
|
encoded_authorization_message |
String |
Encrypted error message. |
Example Request
Enabling automatic provisioning and automatic SCIM synchronization
POST https://{hostname}/v1/identity-stores/{identity_store_id}/provision-tenant
Example Response
Status code: 201
Successful
{
"creation_time" : 1754277890722,
"scim_endpoint" : "https://scim.cn-north-4.myhuaweicloud.com/e0d69be4-ee68-4653-97e4-9e8xxxxx/scim/v2/",
"tenant_id" : "e0d69be4-ee68-4653-97e4-9exxxx"
}
Status Codes
|
Status Code |
Description |
|---|---|
|
201 |
Successful. |
|
400 |
Bad request. |
|
403 |
Forbidden. |
Error Codes
For details, see Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.