Repository navigation
SAML: add more explaination for IdP configurations - #12048
Karuna-Mendix wants to merge 6 commits into
Conversation
| * **Easy configuration** – Uses mostly the defaults provided by the SAML module and supports a single IdP. | ||
| * **Custom configuration** – Uses a custom microflow defined at design time. Supports multiple IdPs and additional customization. | ||
|
|
||
| From SAML module version 4.2.0, the `IdPConfiguration_MicroflowName` constant determines which microflow provides the IdP configuration. Its default value is `SAML.Default_CreateIDPConfiguration`. For custom configuration, specify a custom microflow that returns a list of IdP configurations. |
There was a problem hiding this comment.
Maybe we should extend by saying that SAML.Default_CreateIDPConfiguration activates the runtime configuration mechanism.
Do you think this is the best place in the document to clarify this?
| There are two deployment-managed options: | ||
|
|
||
| * **Easy configuration** – Uses mostly the defaults provided by the SAML module and supports a single IdP. | ||
| * **Custom configuration** – Uses a custom microflow defined at design time. Supports multiple IdPs and additional customization. |
There was a problem hiding this comment.
Custom configuration – Uses a custom microflow defined at design time to create one or multiple IdP configurations when the application starts. It allows you to customize IdP-specific settings while continuing to use applicable defaults provided by the SAML module.
| There are two deployment-managed options: | ||
|
|
||
| * **Easy configuration** – Uses mostly the defaults provided by the SAML module and supports a single IdP. |
There was a problem hiding this comment.
Easy configuration – Uses configuration values defined at design time or overridden at deploy time to create a single IdP configuration when the application starts. It uses sensible defaults provided by the SAML module.
|
|
||
| From SAML module version 4.2.0, the `IdPConfiguration_MicroflowName` constant determines which microflow provides the IdP configuration. Its default value is `SAML.Default_CreateIDPConfiguration`. For custom configuration, specify a custom microflow that returns a list of IdP configurations. | ||
|
|
||
| ### Runtime Configuration |
There was a problem hiding this comment.
heading should be "Manual Configuration through the Administration UI"
|
|
||
| ### Runtime Configuration | ||
|
|
||
| With runtime configuration, an administrator configures one or more IdPs through the Administration UI after deployment. This lets you deviate from the defaults and makes it easier to configure and test SAML settings iteratively without redeploying the application. It is particularly useful during initial setup and troubleshooting. |
There was a problem hiding this comment.
Maybe: "Manual configuration – Configure one or multiple IdPs manually through the Administration UI after the application has been deployed. This supports interactive configuration and testing without redeploying the application."
|
|
||
| The following table compares the easy, custom, and runtime configuration options. | ||
|
|
||
| | | [Easy](#easy-flow) | [Custom](#non-default) | [Runtime](#runtime-config) | |
| | Best suited for | Single IdP, automation and reuse | Multiple IdPs or customized configuration, with automation and reuse | Interactive setup and iterative configuration | | ||
| | Design time | Set default values for the [eight configuration constants](#setup-eight-constants) in the app | Define custom configuration microflow | No IdP configuration required at design time | | ||
| | Deploy time | Override the design-time values where environment-specific settings are required | Provide environment-specific settings | No IdP configuration required at deploy time | | ||
| | Runtime | IdP configuration is created at startup. Changes made through the Administration UI are overwritten at restart. | IdP configuration is created at startup. Changes made through the Administration UI are overwritten at restart. | Configure through Administration UI | |
There was a problem hiding this comment.
improved row:
At application startup | IdP configuration is created from the configured values | Custom microflow creates one or multiple IdP configurations | Existing manually managed configuration is used
https://mendix.slack.com/archives/C033TNDL396/p1791269751037679