Postman Collection and Environment
The post-provisioning customer walkthrough is available as a Postman collection. It ships in the deployment repository under postman/. Install the license and complete platform setup in the Admin Console UI first. The collection starts after that point and covers operator sign-in, tenant onboarding, tenant runtime discovery, issuer configuration, credential design, issuance, DCQL binding, status lists, and verification.
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.
- Use the Admin Console UI to install the license and complete platform setup.
- Fill in the seed environment values:
baseDomain,tenantSlug,tenantName, and the platform operator credentials. - Run operator sign-in, tenant onboarding, and tenant runtime service discovery first. These folders derive
platformUrl,tenantGatewayUrl, redirect URIs, service API base URLs, audiences, tenant ids, issuer ids, and the verifier party id from the platform runtime-config and platform-config APIs. - After discovery has run, the resource folders can be rerun independently when their own prerequisite ids already exist. For example, DCQL binding needs a created DCQL query and the discovered verifier party id; issuing needs the credential design ids, status list id, and tenant runtime service token.
| Variable | Meaning |
|---|---|
baseDomain | Customer-controlled base domain. The gateway must terminate TLS for platform.<baseDomain> and *.<baseDomain>. |
tenantSlug, tenantName | Tenant identity used by the onboarding folder. The tenant gateway host is <tenantSlug>.<baseDomain>. |
operatorEmail, operatorPassword | Platform operator credentials used for sign-in and tenant administration. |
The collection deliberately does not ask you to maintain separate KMS, DID, issuer, verifier, AS, DCQL, credential-design, or status-list URLs. It derives those from baseDomain, tenant onboarding output, and /api/platform/bootstrap/v1/runtime-config/admin-console, then stores the discovered API bases as collection variables for later folders.