An open source Authentication and User Management platform for B2B and B2C.
Full Changelog: https://github.com/teamhanko/hanko/compare/backend/v0.10.2...backend/v0.11.0
email
JWT claim is present on user creation.Full Changelog: https://github.com/teamhanko/hanko/compare/backend/v0.10.1...backend/v0.10.2
Full Changelog: https://github.com/teamhanko/hanko/compare/backend/v0.10.0...backend/v0.10.1
This release contains some highly requested new features:
It is now possible to configure webhooks. For now, subscribable events are limited to changes to user accounts. More information here.
Automatic account linking can now be activated for individual 3rd-party OAuth connections. This allows for existing accounts to be accessed with 3rd-party connections like Sign in with Google when using the same email address, and vice versa.
When a new passkey is created, the original passkey name displayed in the list of passkeys in the user profile is generated by Hanko Backend. Previously, all passkey names looked like "Passkeys-ABCDE", where "ABCDE" was the last characters of the random credential ID. From now on, the passkey names are based on the available information about the authenticator used to create the passkey, e.g. "iCloud Keychain", "Windows Hello" or "1Password", which improves the usability of the passkey list in the user profile.
Full Changelog: https://github.com/teamhanko/hanko/compare/backend/v0.9.1...backend/v0.10.0
Lots of small improvements and fixes in this one.
A big thank you to all contributors.
Full Changelog: https://github.com/teamhanko/hanko/compare/backend/v0.9.0...backend/v0.9.1
This release includes two exciting features that further expand the scope of Hanko:
example.com,
each user that enters an @example.com
email address into the username field of the hanko-auth
element will be redirected to the respective SAML IdP. If the user can be authenticated by the IdP, they will get directed back to Hanko and a regular Hanko JWT will be issued.hanko-profile
actions are still possible for SAML-provisioned users. That means that a SAML user can still create a passkey directly with the service running Hanko and will be able to use this passkey to authenticate without being redirected to the IdP. We are aware that this may not be the desired behavior and we're open to hear your thoughts moving forward.[!IMPORTANT] We've introduced the /ee folder in the Hanko backend that has a different proprietary license for the code that handles SAML SSO connections. Self-hosting a Hanko production deployment that uses /ee code requires a commercial agreement with us. If the SAML feature is not used / configured, the code won't be executed and there's no risk of a license violation.
user export
subcommand by @IgnisDa in https://github.com/teamhanko/hanko/pull/1097
Full Changelog: https://github.com/teamhanko/hanko/compare/@teamhanko/[email protected]/v0.9.0
This is another minor release containing new content for our docs (that have been migrated to Mintlify and their own repo in the meantime) and a few other neat changes:
Full Changelog: https://github.com/teamhanko/hanko/compare/backend/v0.8.3...backend/v0.8.4
This minor release brings some new and handy features, most importantly:
Full Changelog: https://github.com/teamhanko/hanko/compare/backend/v0.8.2...backend/v0.8.3
Another minor release with some fixes and improvements.
Full Changelog: https://github.com/teamhanko/hanko/compare/backend/v0.8.1...backend/v0.8.2
Small release containing some minor features and bugfixes.
Full Changelog: https://github.com/teamhanko/hanko/compare/backend/v0.8.0...backend/v0.8.1