Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove Mx10 instances #9283

Draft
wants to merge 2 commits into
base: Mendix-11
Choose a base branch
from
Draft

Remove Mx10 instances #9283

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c3df3e4
Remove Mx10 instances
ConnorLand Mar 31, 2025
972cddc
Add area where info goes
ConnorLand Mar 31, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 2 additions & 11 deletions .../en/docs/appstore/use-content/platform-supported-content/modules/SAML/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -153,7 +153,8 @@ There are different versions of the SAML module, depending on which version of M

Mendix 10 does not support the 2.0 version of the Atlas UI, so you should never use the even-numbered (Atlas 2.0-compatible) SAML patch releases with your Mendix 10 app.

{{% todo %}} Do we need to add anything here for Mendix 11? {{% /todo %}}
* For Mendix 11, you should ...
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need widget/styling SMEs to help me write this.



3. To download the required release, in the **Releases** tab, find the release that is compatible with your app per the guidelines in the **Documentation** tab, and then click the **Download** button by the number of the release.
4. Follow the instructions in [How to Use Marketplace Content](/appstore/use-content/) to import the SAML module into your app.
Expand All @@ -169,16 +170,6 @@ By default, the SAML module will be installed as the **SAML20** module in your a
* **DefaultLoginPage** – You can specify a different login page when the login process fails. When the end-user cannot be authenticated in the external IdP, a button will appear, and by clicking this button, they will be redirected to the specified login page. If this is left blank, an unauthenticated user will be redirected to `/login.html`.
* **DefaultLogoutPage** – Removing the sign-out button is recommended, but if you keep it, the end user will be redirected to a page. You can choose where the end-user is redirected to (for example, back to `/SSO/` or your `login.html` page). Every user signed in via SAML is redirected to this location when logged out.
* **SSOLandingPage** – Set this if you redirect the `index.html` to log into your app automatically. See [Using SSOLandingPage](#ssolandingpage) for further information about this.
* **HybridAppLoginTimeOutInMinutes** –
* If you use the default login handler in your [hybrid mobile](/refguide9/mobile/introduction-to-mobile-technologies/hybrid-mobile/) app, you must change the `com.mendix.webui.HybridAppLoginTimeOut` custom runtime setting to change the validity of the authentication token used by the hybrid mobile app.
* If you use the SAML module in your hybrid app, you must change the `SAML20.HybridAppLoginTimeOutInMinutes` constant to change the validity of the authentication token used by the hybrid mobile app.
* If you use both the default login handler and the SAML module in your hybrid app, you must change both so that they match. This is because, when you use the SAML module for SSO in your Mendix app, the authentication token is not created by the Mendix runtime, which uses the custom runtime setting. Instead, the authentication token is created by the Java code in the SAML module. This Java code does not have access to the custom runtime setting value and thus requires the constant value to be set.

Only use this setting if you are using SAML on a hybrid mobile app. Note that this functionality also requires mobile authentication tokens to be enabled in your IdP Configuration as well as changes to the hybrid app package as described in [How To Implement SSO on a Hybrid App with Mendix and SAML](/howto8/mobile/implement-sso-on-a-hybrid-app-with-mendix-and-saml/).

{{% alert color="warning" %}}Hybrid mobile apps are not available in Mendix 10.{{% /alert %}}
{{% todo %}} How about in Mendix 11? {{% /todo %}}

5. Sign in to the application and configure the SAML module as described in the [Configuration SAML Module](#config) section.

### Using SSOLandingPage{#ssolandingpage}
Expand Down
2 changes: 1 addition & 1 deletion ...ent/en/docs/refguide/mobile/using-mobile-capabilities/native-language-change.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ While this guide gives your end-user the ability to switch their app's language,

Before starting this guide, make sure you have completed the following prerequisites:

* Install Mendix Studio Pro version [9.14.0](/releasenotes/studio-pro/9.14/) or above
* Install Mendix Studio Pro version [11.0](/releasenotes/studio-pro/11.0/) or above
* Complete the [Prerequisites](/refguide/mobile/distributing-mobile-apps/building-native-apps/deploying-native-app/#prerequisites) section of *Build a Mendix Native App in the Cloud*
* Make sure your [Nanoflow Commons](/appstore/modules/nanoflow-commons/) module is up to date
* Read the [Language Menu](/refguide/translatable-texts/) guide to understand the basics of the Mendix Language menu
Expand Down