Review the tenant authorization servers
Step 1 of 4 in Configure the authorization server.
Start with the authorization servers your tenant can use. This list comes from the authorization server service itself and is tenant-scoped: the tenant is taken from your access token, so you only ever see your own servers.
Each item carries the server id, its display name and lifecycle status, and the public issuer a
wallet or client sees, with links to its administration record. Results are paged with cursor and
limit. Nothing secret is returned: client secrets, signing keys and upstream credentials never
appear.
The administration record holds the full configuration. Read it through the platform configuration API with the same id:
A newly provisioned tenant has one hosted default server, normally in LOCAL_ONLY authentication
mode. Each entry carries the administration UUID, slug, public issuer, deployment
(HOSTED or EXTERNAL), purposes, lifecycle status and a revision. Use the UUID in every later
path; never reconstruct it from the slug or the issuer URL.
purposes (GENERAL, CREDENTIAL_ISSUANCE, WALLET_LOGIN) record what the server is for;
they do not gate selection. An issuer can bind any active server of the tenant whose
allowedGrantTypes include an OID4VCI grant.
Next
Continue with step 2, Create and activate a hosted server.