WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

v2.2.0 🚀

Choose a tag to compare

View all tags
@github-actions github-actions released this 30 Oct 02:35
· 2 commits to refs/heads/main since this release
v2.2.0
a729783
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Release v2.2.0

🎉 New Features

Keycloak Groups and Roles in Custom Data

This release automatically passes Keycloak user groups and roles to Authsignal, enabling more sophisticated authentication rules based on user permissions and group memberships.

What's included:

  • keycloakGroups - User's group memberships
  • keycloakRoles - User's realm-level roles
  • keycloakClientRoles - User's client-level roles

Use Cases:

  • Implement group-based access policies (e.g., require additional verification for "Admin" group)
  • Apply different authentication rules based on user roles
  • Create step-up authentication flows for privileged roles
  • Build conditional MFA requirements based on permissions

Getting Started:

  1. Set up custom data points in your Authsignal portal for keycloakGroups, keycloakRoles, and keycloakClientRoles
  2. Create rules in Authsignal that reference these custom attributes
  3. Deploy the updated plugin - groups and roles will automatically be included in authentication requests

No code changes required on your end - this data is automatically sent with every authentication request.

Full Changelog: v2.1.5...v2.1.6

Assets 2
Loading