Issue
In SAML module version 4.2.0 and later, the Use custom logic for user provisioning checkbox in the SAML20.UserProvisioning_Mapping snippet cannot be enabled.
The checkbox is bound to the SSOConfiguration.UseCustomLogicForProvisioning attribute. However, the row containing the checkbox has a visibility condition that only makes it visible when this same attribute is set to true.
Since the attribute defaults to false and there is no other way within the module to change its value to true, the checkbox is never displayed on a newly created SSO configuration. Similarly, if the option is unchecked on an existing configuration, the checkbox disappears and cannot be enabled again.
This creates a circular visibility condition that prevents enabling or re-enabling custom logic for user provisioning through the module's user interface.
Environment
SAML v4.2.0 and newer
Cause
This is not a bug. The behavior follows from the deprecation of the legacy custom user provisioning logic in the SAML module:
- Starting with SAML module version 4.0.0, the legacy custom user provisioning microflow is deprecated.
- As of SAML module version 4.2.0, the legacy custom user provisioning microflow is removed and no longer supported.
Solution/Workaround
Custom user provisioning is supported through the Custom UserProvisioning field in the User Provisioning tab.
Starting from SAML module version 4.2.0, the old custom provisioning microflow is no longer available for selection. The new microflow can be configured similarly to the old one through the SAML configuration.
Only the new custom user provisioning microflow can be selected.
There are two main differences when configuring the new custom microflow:
-
Microflow Naming Convention
- The microflow name must start with
UC_. - Only microflows that follow this naming convention will appear in the SAML configuration dropdown.
- The microflow name must start with
-
Required Input Parameters
- The microflow must have the following input parameters:
UserInfoParameter(UserCommons.UserInfoParam)User(System.User)
- If the microflow name starts with
UC_but the input parameters do not match the required signature, the microflow may not function correctly.
- The microflow must have the following input parameters:
For more information, please refer to Section 1.4.3 of the SAML documentation.
Internal information related
- 287915, 292125
- C03HEV4LK1C/p1789471072241579
Additional information
Mendix documentation: CustomUserProvisioning
Marketplace content: SAML module
0 Comments