Release 233 (15.02.2025)

Release 233 introduces a new User Attribute Mapping configuration for SAML and OAuth single sign-on connections, making it easier to align identity-provider attributes with Priverion user fields. It also improves stability of the company-selection step during login.

New Release

Version: 233
Release Date: 15.02.2025 19:00 CET


Overview

This release adds a dedicated User Attribute Mapping panel to the SAML / OAuth SSO configuration screen, allowing administrators to define how identity-provider attributes are mapped to Priverion user fields and to set a unique identifier for each user. In addition, the company-selection dropdown during login has been made more robust, and the default source ID for SAML2 connections is now set automatically.

Contents

  • What's new
  • Improvements
  • Fixes

What's new

User Attribute Mapping for SAML / OAuth SSO [NG-3620, NG-3621]

A new User Attribute Mapping section is now available when creating or editing a SAML or OAuth SSO connection under IT Settings → IAM. Administrators can:

  • Map identity-provider attributes (e.g. first name, last name, e-mail, groups) to the corresponding Priverion user fields.
  • Designate a Unique Identifier — the attribute that uniquely identifies each user in the identity provider.
  • Mark individual mappings as optional where a value is not always present.
  • Use a pre-filled template for common providers (e.g. Microsoft Entra ID / Azure AD) to reduce manual configuration effort.

Mandatory fields are validated before saving; clear error messages are shown if required mappings are missing.

Automatic source ID for SAML2 connections [NG-3620]

When adding a new SAML2 SSO connection, the unique identifier source is now pre-set to Assertion Subject NameID by default, reducing the number of manual steps required during initial configuration.

Improvements

  • IT Settings → IAM → SCIM: Group claims are now automatically enabled or disabled based on whether Microsoft Entra ID synchronisation is active, preventing conflicting configurations.
  • Login — company selection: The company-selection dropdown that appears during SSO login is handled more gracefully; transient visibility issues no longer cause the login flow to fail.

Fixes

  • Fixed optional-chaining errors for providerKey and protocol fields in the SSO attribute mapping form that could cause the screen to crash under certain configurations. [NG-3620]
  • Fixed validation of mandatory SSO fields to correctly account for group-claims configuration, avoiding false "missing field" errors. [NG-3624]

Known issues

No known issues.

Feedback and Support

We value your feedback. If you encounter any issues or have suggestions, please contact our support team:

  • Schedule a Meeting: Via the Help Widget
  • Give Feedback with Screenshots: Via the Feedback Button in the Help Widget
  • Schedule a Support Call: Here
  • Schedule a Technical Support Call: Here

Was this article helpful?