Repository navigation
OAuth client policies
Global administrators can require PAR, PKCE, and DPoP, restrict client authentication methods, and cap configured token lifetimes across OAuth and OIDC applications or by application type. Set clientPolicies through the settings API.
The application creation API also accepts public keys for clients that authenticate with private_key_jwt.
Compatibility and testing
- Dynamic registration accepts unused public-key metadata from shared-secret clients.
- The updater verifies the published Compose image tags and refuses to downgrade an installation.
- Six OpenID Connect conformance plans matched the published results after the dynamic registration rerun, with zero failed modules. The suite results are self-tested.
- The conformance harness can use a different Docker subnet when the default overlaps an existing network.
Upgrade
Back up PostgreSQL and HALO_SECRET_KEY before upgrading. Use ghcr.io/scalastudios/halo-server:0.3.0 and ghcr.io/scalastudios/halo-web:0.3.0 together. The release's Compose file and Helm chart default to these images. Follow the README's upgrade instructions for an existing installation.