Skip to content

Releases

Halo v0.3.0

Choose a tag to compare

@ohemilyy ohemilyy released this 21 Nov 22:25
1fb0904

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.

Full changelog · Compare v0.2.0…v0.3.0

Halo v0.2.0

Choose a tag to compare

@ohemilyy ohemilyy released this 21 Nov 19:46
9b723d7

Halo v0.2.0 expands identity controls, application protocols, and self-hosting support.

  • Require identity proof before an invitation or sign-up becomes active, with in-person and provider checks.
  • Use signed client assertions, pushed authorization requests, DPoP, and a per-application FAPI 2.0 profile. Mutual TLS client authentication remains open.
  • Run multiple Halo instances on one PostgreSQL database, with coordinated background jobs and a readiness endpoint.
  • Connect directories and infrastructure through LDAP, RADIUS, Kerberos, SSH certificates, and POSIX host login. Store signing keys in Vault or cloud KMS. PKCS#11 is available in builds that enable it.
  • Run the OpenID Foundation conformance suite against Halo. Six local test plans had zero failed modules, and all twenty visual review cases were checked in Chromium. The independent audit and OpenID certification remain open.

The server and web images are published as ghcr.io/scalastudios/halo-server:0.2.0 and ghcr.io/scalastudios/halo-web:0.2.0. Back up PostgreSQL and the Halo secret key before upgrading. Use the same version for both images.

Changes since v0.1.1 · Conformance report