loading
Preparing LoginRadius developer resources
Mission: Help enterprises accelerate digital transformation with our fully-managed Customer IAM technology.
Skip to main content

Core API Release 37.8.0

· 2 min read

This release of the LoginRadius core api introduces new features and improvements.

Changelog

Added

  • Workflow Versioning — You can now view and revert to any of the last 10 workflow versions directly from the Admin Console. This makes it easy to track changes over time, compare configurations, and quickly roll back to a previous version if a recent update causes unexpected behavior.

  • Shared State API for Workflow Scripts — A new shared state (errorObject.session.sharedState) is available within workflow scripts, allowing you to pass data seamlessly between different nodes in a workflow. This is especially useful for building complex, multi-step authentication or registration flows where downstream nodes need access to data set by earlier nodes.

  • Disable Hosted Pages — A new option has been added to disable the default hosted pages at the /auth and /profile routes. When disabled, requests to <tenant>.hub.loginradius.com will return a forbidden response. This is ideal for customers who use fully custom login UIs and want to prevent end users from accidentally accessing the default hosted pages.

  • Strong Customer Authentication (SCA) with IO Workflow — PSD2-compliant SCA orchestrated through IO Workflow. This includes support for Pushed Authorization Requests (PAR) and Rich Authorization Requests (RAR), along with Dynamic Linking and Push MFA/Passkey verification. Upon successful authentication, authorization_details and linking_id are returned in the ID token.

Improved

  • Signed UserInfo (JWT) in Custom OAuth IDP — UserInfo now supports signed JWT responses validated via JWKS endpoint.

  • Extended profile field mapping in Custom OAuth — Additional profile fields, including Address and PhoneNumbers, are now available for mapping in Custom OAuth provider configurations.

  • Username support in Auth Resend Email API — The Auth Resend Email Verification API now accepts the username parameter in addition to the existing email-based lookup.

  • Standardized scope claim in JWT access tokens — The scope claim in JWT access tokens has been renamed from SCP to scope to align with the IETF standard (RFC 9068). If your application or any downstream integrations read the scope claim from LoginRadius-issued access tokens, please update them to reference the new scope claim name to avoid any disruptions.

Please reach out to LoginRadius Support for any further queries.