Description of the enhancement/bug
Add xuser_type and xuser_id fields to CreateOpts in openstack/identity/v3.0/users/CreateUser.go.
Current Behaviour
The CreateOpts struct does not expose xuser_type and xuser_id, even though the OTC IAM API (POST /v3.0/OS-USER/users) accepts both fields. These fields are present in the User response struct and in UpdateAdminOpts, but cannot be set at creation time via the SDK.
Desired Behaviour
CreateOpts should include XuserType and XuserID so that callers can create IAM users with external identity mapping in a single atomic API call.
API Reference
See: https://docs.otc.t-systems.com/identity-access-management/api-ref/apis/user_management/creating_an_iam_user_recommended.html
Relevant request body fields:
| Field |
Type |
Constraint |
xuser_type |
String |
Optional. Must be used together with xuser_id. Currently only "TenantIdp" is supported. |
xuser_id |
String |
Optional. Must be used together with xuser_type. Max 128 characters. |
Description of the enhancement/bug
Add
xuser_typeandxuser_idfields toCreateOptsinopenstack/identity/v3.0/users/CreateUser.go.Current Behaviour
The
CreateOptsstruct does not exposexuser_typeandxuser_id, even though the OTC IAM API (POST /v3.0/OS-USER/users) accepts both fields. These fields are present in theUserresponse struct and inUpdateAdminOpts, but cannot be set at creation time via the SDK.Desired Behaviour
CreateOptsshould includeXuserTypeandXuserIDso that callers can create IAM users with external identity mapping in a single atomic API call.API Reference
See: https://docs.otc.t-systems.com/identity-access-management/api-ref/apis/user_management/creating_an_iam_user_recommended.html
Relevant request body fields:
xuser_typexuser_id. Currently only"TenantIdp"is supported.xuser_idxuser_type. Max 128 characters.