Skip to content

0factor 0.1.2

Choose a tag to compare

View all tags
@c4l3b c4l3b released this 14 Oct 23:23
v0.1.2
757117d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

0factor 0.1.2 fixes login display names and dashboard links, and lets applications preserve existing identities when migrating from another mock OIDC provider.

  • Login cards fall back to claims.name, then claims.given_name, when first and last names are absent.
  • Verify native submit-button semantics and plain-form sign-in for user cards.
  • Give existing unlabeled dashboard discovery links readable names such as shop discovery, without adding duplicate links.
  • Add ZF_ISSUER to preserve the exact issuer in discovery and signed tokens, including root issuers and trailing slashes. Realm endpoint URLs continue to use ZF_HOSTNAME or the request URL.
  • Document migration configuration and bump ZeroFactor.Aspire.Hosting to 0.1.2.

Migrating from a root-issuer mock

Set ZF_ISSUER to the exact old issuer and preserve imported user IDs to keep (iss, sub) identity keys. Configure your client's MetadataAddress to the realm discovery URL, for example http://localhost:8080/realms/shop/.well-known/openid-configuration, and keep issuer validation enabled. The override applies to every realm; use a single realm when preserving identities from another mock. See the migration guide.

Publishing this release triggers matching artifacts:

Validation: 80 .NET tests, including the Aspire container end-to-end flows; 6 iframe tests; Native AOT builds.

0factor is for local development only.

Full changelog

Assets 2
Loading