Version: v0.25.0 (Latest)
Postman Collection and Environment
The complete walkthrough is available as a Postman collection. It ships in the deployment repository under postman/. Every page in this section corresponds to a collection folder with the same number, and the examples shown in the documentation are produced by running this collection.
The same files are available here for direct download:
- EDK-Enterprise-Deployment.postman_collection.json
- EDK-Enterprise-Deployment.customer.postman_environment.json
Using the collection
- Import both files into Postman and select the environment.
- Fill in the environment values: the service base URLs, your license token, the platform operator credentials, the tenant service client secret, and your did:web domain.
- Run the folders in order, either request by request or with the Collection Runner. Later folders consume identifiers captured by earlier ones (tenant id, DID, design ids, status list id), so order matters.
| Variable | Meaning |
|---|---|
platformUrl, kmsUrl, didUrl, asUrl, issuerUrl, verifierUrl | Base URLs of the services. With the gateway model, platformUrl is https://platform.<base-domain> and tenant services are reached through tenant hosts such as https://acme.<base-domain>. |
tenantServiceClientId, tenantServiceClientSecret | Confidential client used to obtain the tenant-AS token for runtime service calls |
didWebDomain | Public domain for the tenant's did:web identifier (must match the DID hosting host) |
issuerPublicHost, verifierPublicHost | Public hosts bound as tenant endpoints |
licenseToken | Your deployment license token |
secretBackend | Secret backend selection for tenant secrets |
idpClientSecret | Client secret of the federation IdP example |
verifierId | Verifier instance id for DCQL bindings |