Skip to content

Commit 0597465

Browse files
Merge pull request mendix#10719 from mendix/kv-saml-updates
SAML updates 4.2.1
2 parents cc634ba + e11271b commit 0597465

1 file changed

Lines changed: 8 additions & 2 deletions

File tree

  • content/en/docs/marketplace/platform-supported-content/modules/SAML

content/en/docs/marketplace/platform-supported-content/modules/SAML/_index.md

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -364,8 +364,13 @@ Deploy your application and log in with the application Admin account. Click **S
364364
#### Configuring Steps
365365

366366
1. Navigate to the **Model Reflection**, select the required module from the left navigation pane, and select **Click to refresh** to synchronize entities and microflows. In version 4.x, refreshing the module is no longer required.
367-
2. In the **SP Configuration** tab, provide the necessary values and click **Save**. You need to complete this step before proceeding with IdP Configuration.
367+
2. In the **SP Configuration** tab, provide the necessary values and click **Save**. Complete this step before proceeding with IdP Configuration.
368368
3. In the IdP Configuration tab, click **New** and provide the necessary details. For more information on IdP configuration tabs, see the [Reference Guide for SAML IdP Configuration](/appstore/modules/saml/idp-attributes/) document.
369+
370+
{{% alert color="info" %}}
371+
The `SAML20.DefaultEntity` constant is used at runtime to prefill the default user provisioning entity when creating a new SAML IdP configuration, with `Administration.Account` set as the default value.
372+
{{% /alert %}}
373+
369374
4. From version 4.0.0 of the SAML module, you have the option to download the SP Metadata from the **Encryption Settings** tab, **Identity Provider Metadata** tab, and at the end of the configuration process.
370375

371376
#### Downloading and Uploading SP Metadata Manually
@@ -499,7 +504,8 @@ It is possible to customize this microflow to determine the correct user. Whiche
499504
#### CustomUserProvisioning {#customuserprovisioning}
500505

501506
{{% alert color="info" %}}
502-
Starting from version 4.0.0 of the SAML module, the `CustomUserProvisioning` microflow is deprecated.
507+
Starting from version 4.0.0 of the SAML module, the `CustomUserProvisioning` microflow is deprecated. To show custom user-facing error messages, call `SAML20.ThrowSAMLFeedbackException` from a custom microflow (`UC_CustomProvisioning`) configured in the **Custom UserProvisioning** field of the **UserProvisioning** tab. For more information, refer to the [Custom User Provisioning at Runtime](/appstore/modules/saml/#custom-provisioning-rt) section above.
508+
503509
{{% /alert %}}
504510

505511
When selecting in the SSO configuration to run the `customUserProvisioning` action (previously known as `CustomLoginLogic`), you can update the new or retrieved user with additional information from the assertion. All the assertions are passed into the microflow in the parameter `AssertionAttributeList`, and these can be transformed and stored in the user record. Also, additional roles can be granted to the users based on the assertion attributes.

0 commit comments

Comments
 (0)