4. Configure Open EPM
Configure the pinned development checkout on the VM before you initialize its fresh database. Obtain the approved issuer and client settings from the identity administrator, and keep service passwords and the preview signing secret in the private environment file.
- Prepare DNS, HTTPS and OIDC and confirm the exact issuer, reachable HTTPS JWKS endpoint, separate audiences and immutable initial operator identity.
- Create the private environment file, match those identity values and check that the development Compose profile resolves.
After the private configuration passes, continue to build and initialization. Follow the signed package path for native Keycloak and gateway deployment.
In this section
- 4.1 Prepare DNS, HTTPS and OIDCVerify issuer discovery and signing keys, and prepare the gateway’s DNS, HTTPS and audiences.
- 4.2 Create the private environment fileCreate the protected environment file and check that the pinned development profile resolves.