Identity & Access Management

Preview — pending review

This reference is generated from the platform API contract and is still under review. Operations, fields, and descriptions can change before publication.

Dry run -- OpenStack credentials an access change would revoke

POST
/tenants/{tenantId}/iam/users/{userId}/access/actions/preview-openstack-credential-impact

Which of the member's ACTIVE OpenStack API credentials the platform would delete if the given PUT (access) or DELETE (removeAssignmentId) were made. Exactly one of the two. The change runs through the same code as the write -- every validation, 403 and 409 included -- inside rolled-back savepoints: nothing is written, staged or published.

Authorization

bearerToken
headerAuthorizationBearer <token>

An API token (pc_live_…) or a service-account key (sak_live_…), created in Identity & Access Management and sent as Authorization: Bearer <token>. Requests are rate limited per credential and per tenant: every response carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset, and a refused request gets 429 RATE_LIMITED with Retry-After.

Path Parameters

tenantId*string

The tenant id.

userId*string

The member (its id is its email).

Request Body

application/json
  1. body

The access change to preview -- exactly one of access (a PUT) and removeAssignmentId (a DELETE).

access?array<>|
Itemsitems <= 500
removeAssignmentId?string|null

Response Body

The credentials the change would revoke (empty when none).

application/json
  1. response
data*array<>
curl -X POST "https://example.com/tenants/string/iam/users/string/access/actions/preview-openstack-credential-impact" \  -H "Content-Type: application/json" \  -d '{}'
{  "data": [    {      "id": "string",      "name": "string",      "projectId": "string",      "profile": "full"    }  ]}