Unable to enable the Use custom logic for user provisioning checkbox in SAML module 4.2.0 and newer versions

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.

Custom user provisioning is now configured through a different mechanism, so the legacy checkbox is no longer meant to be enabled on SSO configurations.

Solution/Workaround

Do not rely on the legacy CustomUserProvisioning microflow. Starting with SAML module version 4.0.0, custom user provisioning is configured instead through the Custom UserProvisioning field on the User Provisioning tab:

1. In the running app, sign in as an administrator, open the SAML configuration page, and select the IdP configuration.
2. Go to the User Provisioning tab.
3. In the Custom UserProvisioning field, select the microflow containing the custom provisioning logic. The microflow name must start with UC_CustomProvisioning, and it must accept a UserInfoParameter (UserCommons.UserInfoParam) and a User (System.User) parameter, returning a System.User.
4. Click Save.

If the app still relies on the legacy custom logic microflow, migrate that logic to a microflow selected in the Custom UserProvisioning field. The legacy microflow is no longer supported in SAML module 4.2.0 and newer versions. 

Additional information

Mendix documentation: CustomUserProvisioning

Marketplace content: SAML module