Please use the form below, leaving the prefilled data to help us. Thank you.
Page link: saml-installation-and-configuration
Document link: saml-installaion-configuration.md
My Issue/Suggestion
I believe that we should call out explicitly in a section here how the cont= parameter behaves regarding deeplinking a specific microflow/page URL.
When creating a deeplink in the properties section of a microflow/page in Studio Pro, it prompts the URL as /p/[insert url here] (see attached screenshot for clarification). In my personal experience, and support engineer experience, this confuses developers as they believe they need to include the entire /p/ in the redirect when instead the URL would correctly be structured as, for example: https://mydomain.com/sso/login?cont=p/workflow/1234. Note that the / is missing from the start of the cont= parameter.
In addition, we could expand the documentation to include how to structure a deeplink redirect with a specific idp included, which would be: https://mydomain.com/sso/login?_idp_id={MyIdPAlias}?cont=p/workflow/1234 another common use case from my developer days.
I think this documentation is necessary now that deeplinking is built into Mendix and since SSO is basically the standard way to use a Mendix app.
Please use the form below, leaving the prefilled data to help us. Thank you.
Page link: saml-installation-and-configuration
Document link: saml-installaion-configuration.md
My Issue/Suggestion
I believe that we should call out explicitly in a section here how the
cont=parameter behaves regarding deeplinking a specific microflow/page URL.When creating a deeplink in the properties section of a microflow/page in Studio Pro, it prompts the URL as
/p/[insert url here](see attached screenshot for clarification). In my personal experience, and support engineer experience, this confuses developers as they believe they need to include the entire/p/in the redirect when instead the URL would correctly be structured as, for example:https://mydomain.com/sso/login?cont=p/workflow/1234. Note that the/is missing from the start of thecont=parameter.In addition, we could expand the documentation to include how to structure a deeplink redirect with a specific idp included, which would be:
https://mydomain.com/sso/login?_idp_id={MyIdPAlias}?cont=p/workflow/1234another common use case from my developer days.I think this documentation is necessary now that deeplinking is built into Mendix and since SSO is basically the standard way to use a Mendix app.