Admin API: Whoami
Operations on whoami in the Odudu admin API, one section each. Every request carries a bearer token; the index says which audience it needs and how a refusal is shaped.
GET /admin/tenants/{tenant}/whoami
Requires an authenticated admin caller.
Path parameters
| Name | Type | Required | Details |
|---|---|---|---|
tenant | string | yes | The tenant being administered, addressed by name. |
Responses
200 OK
Body: application/json
| Field | Type | Required | Details |
|---|---|---|---|
subjectId | string | yes | The subject the access token was issued to. |
issuerTenantId | string | yes | The tenant that issued the token, which is the caller’s own tenant. |
capabilities | array of string | yes | The admin capabilities the caller holds in its own tenant, directly, through a group or nested in a role. A composite such as tenant-admin is reported as the capabilities it carries. |
crossTenant | boolean | yes | True when the caller’s tenant is not the tenant in the path, which only a holder of manage-tenants may be. |
401 RFC 9457 problem details
Body: application/problem+json, an RFC 9457 problem document described under problem details.
Documentation coverage: 4 of 4 fields described (100%).