Release v1.2.8

🚀 Release: Keycloak-Compatible Registration Prefill

This release delivers a robust registration prefill implementation that works with real Keycloak redirect behavior.

What’s New

• Added optional registration field prefill using snake_case field keys.
• Introduced a Keycloak-compatible transport via login_hint JSON payload.
• Kept plain login_hint support as alias for username and email.
• Added Storybook scenarios for:
  • successful prefill from login_hint JSON
  • non-overwrite behavior when values already exist

Why This Change

Keycloak may strip arbitrary query parameters during redirects.
To make prefilling reliable in production, this release supports structured data passed through login_hint.

Feature Flag

Enable the feature explicitly:

TAILCLOAKIFY_ENABLE_REGISTRATION_URL_PREFILL=TRUE

Supported Payload Format

Use snake_case keys inside login_hint JSON:

https://id.example.com/realms/my-realm/protocol/openid-connect/registrations?login_hint=%7B%22first_name%22%3A%22Max%22%2C%22last_name%22%3A%22Mustermann%22%2C%22email%22%3A%22max%40example.com%22%2C%22username%22%3A%22max-user%22%7D

Behavior and Safety

• Disabled by default.
• Existing Keycloak-provided values are never overwritten.
• Password fields are never prefilled.
• Custom fields are supported via snake_case field names in the payload.
  Full Changelog: v1.2.7...v1.2.8