Skip to main content

Core 7.5.1 Release Notes

SSO Updates for Large User Libraries & Migrating Existing Accounts

This release delivers security hardening, Single Sign-On (SSO) improvements, and a more seamless admin experience.

Security enhancements

  • MFA setting bypass resolved — Admins can no longer save Multi-Factor Authentication changes without completing authentication. Previously, changes saved automatically before the auth check was completed.

  • SSO admin re-authentication streamlined — Admins logged in via SSO are no longer prompted for redundant re-authentication when making account changes. Security is enforced through their SSO provider. This change enables Admin accounts to now be SSO-based.

  • SSO user profile fields protected — Fields populated by customers' identity provider (IDP) can no longer be overridden or accidentally altered through the platform UI.

  • Geolocation data updated — The underlying IP-to-country database has been refreshed, ensuring more accurate location tracking in the platform's action log.

SSO improvements

  • Clearer SSO error messages — When there's a login issue with the identity provider, users now see a clear, descriptive error instead of a generic failure screen.

  • Password reset for SSO users improved — Attempting to reset a password for an SSO user now returns a clear, informative message instead of an error.

  • Deleted SSO users can re-register cleanly — If an admin removes an SSO user and they log back in, a fresh account is created without inheriting any data or roles from the deleted account. The new user account has no permissions by default.

  • SSO users no longer prompted for email verification — Users signing in via SSO for the first time are no longer shown an unnecessary email verification step.

  • Account conversion supported — Existing standard user accounts can now be migrated and converted to SSO accounts.

  • SSO ID field permissions tightened — Manually editing a user's SSO ID no longer inadvertently changes their account type from a standard account to an SSO account.

Under the hood

  • Improved diagnostic logging — Internal API logging has been enhanced to make troubleshooting SSO and user provisioning issues faster and more reliable.

  • Re-authentication logic standardized — The decision to prompt for re-authentication is now consistently driven by the backend, eliminating mismatches between what the UI showed and what the server required.

Did this answer your question?