Skip to content

Commit cc9485c

Browse files
committed
Merge branch 'development' into yl-proofread-microflow-and-nanoflow-documentation
2 parents c7735c9 + 24c77c6 commit cc9485c

122 files changed

Lines changed: 2596 additions & 1362 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

content/en/docs/apidocs-mxsdk/apidocs/catalog/search-api.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -282,4 +282,4 @@ A successful `GET` call results in a `200` status code and a JSON response body
282282

283283
## API Reference {#api-reference}
284284

285-
{{< swaggerui src="/openapi-spec/catalog-registration_v5.yaml" >}}
285+
{{< swaggerui src="/openapi-spec/catalog-search_v5.yaml" >}}

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

Lines changed: 601 additions & 0 deletions
Large diffs are not rendered by default.
Lines changed: 63 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,63 @@
1+
---
2+
title: "Advanced configuration for SAML"
3+
url: /appstore/modules/saml/advanced-configuration
4+
weight: 20
5+
description: "Describes the advanced configuration for the SAML module"
6+
#If moving or renaming this doc file, implement a temporary redirect and let the respective team know they should update the URL in the product. See Mapping to Products for more details.
7+
---
8+
9+
## Introduction
10+
11+
This document outlines the advanced configurations for the SAML module. For basic configuration and usage, refer to the [SAML](/appstore/modules/saml/) documentation.
12+
13+
### Multi-tenant Behavior
14+
15+
The resource folder contains a file called *SAMLConfig.properties*. In this file, you can optionally override advanced settings from the SAML module. Usage of this file is optional. When the file does not exist or you do not specify a setting, the module will use its default behavior.
16+
This file contains the documented properties, and example lines show the default values of these options.
17+
With these settings, you can configure the behavior of this module and improve the multi-tenant behavior of your application. For plain SAML authentication, it is best to leave this file unchanged.
18+
19+
### Use a Certificate Issued by a Certificate Authority {#use-ca}
20+
21+
By default the SAML SSO module will use self-signed certificates. It is, however, also possible to use certificates issued by a certificate authority (CA).
22+
23+
SAML SSO supports 2 file formats:
24+
25+
* a PKCS 12 file, which typically has extension .pfx or .p12.
26+
* a jks file.
27+
28+
To use a CA-certificate, upload it as your key store file as described in [Managing the Keys and Key Store](/appstore/modules/saml/idp-attributes/#keystore).
29+
Remember to do the following:
30+
31+
* set the certificate password in the `KeystorePassword` constant of your app to be able to read the contents of the uploaded key store.
32+
* use an alias for the certificate — this must be the name parameter that is provided when creating the certificate you are uploading. If the values do not match, the SAML module will fall back to using a self-signed certificate instead.
33+
* the value of the configured SP EntityID must match the alias that is included in the uploaded key store.
34+
35+
### Customizing the Login Page
36+
37+
Mendix runtime/system module comes with a default login page. When using SAML with a single IdP, this page is not required.
38+
You need to customize this login page when end-users have different ways of login:
39+
40+
1. If you want to use both Mendix (local) login and SSO login:
41+
42+
1. Go to the **App** > **Show App Directory in Explorer** > **theme/web** folder (for Mendix versions below 9.0.0, this is the **theme** folder).
43+
2. Rename `login.html` to `login-without-sso.html`.
44+
3. Rename `login-with-mendixsso-button.html` to `login.html`.
45+
4. Open login.html, update the **href** to `/SSO`, and give a button name
46+
47+
Your app is now configured to use Mendix SSO login.
48+
2. If you want to connect your app with multiple IdPs and the end-user of your app needs to select the IdP to use for login.
49+
Follow the steps below:
50+
51+
1. Go to the **App** > **Show App Directory in Explorer** > **\implementation\DiscoveryHandler.java**
52+
2. Find the template **saml2-discovery-binding.vm** and add your customization.
53+
54+
### Custom Settings
55+
56+
The resources folder contains the *SAMLConfig.properties* file, and through this file, advanced settings can be configured for the module. This file contains the settings along with documentation on the settings. Through this file, it is possible to alter the URLs used as well as how the application behaves in a multi-tenant environment. The file also specifies all the default values and behavior in more detail.
57+
58+
If you are using a custom URL, see [How Do I Get my SAML Metadata or CommunityCommons.GetApplicationUrl to Use the Custom URL?](/developerportal/deploy/custom-domains/#use-custom-url) in the *Custom Domains* documentation.
59+
60+
## Read More
61+
62+
* [OIDC SSO](/appstore/modules/oidc/)
63+
* [Reference Guide for SAML IdP Configuration](/appstore/modules/saml/idp-attributes/)

content/en/docs/appstore/use-content/platform-supported-content/modules/SAML/idp_attributes.md

Lines changed: 204 additions & 0 deletions
Large diffs are not rendered by default.

content/en/docs/appstore/use-content/platform-supported-content/modules/aws/amazon-bedrock.md

Lines changed: 54 additions & 110 deletions
Large diffs are not rendered by default.

content/en/docs/appstore/use-content/platform-supported-content/modules/database-replication.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -158,9 +158,13 @@ This determines whether values in this column should be interpreted as case sens
158158

159159
### Custom Query
160160

161-
If you selected **Custom** as the query type, you can enter a custom select value for the field. This enables constructing a complex value for the mapped field. For example, you can concatenate multiple database columns together. The **Join tokens** table (below the query field) shows the tokens representing the tables you joined using the **Include additional tables** tab. You can insert these into your query and they will be replaced by the proper table names. Keep in mind that this query must be provided in the dialect from the database from which you are retrieving the data.
161+
If you selected **Custom** as the query type, you can enter a custom select value for the field. This enables constructing a complex value for the mapped field. For example, you can concatenate multiple database columns together. The **Join tokens** table (below the query field) shows the tokens representing the tables you joined using the **Include additional tables** tab. You can insert these into your query and they will be replaced by the proper table names.
162162

163-
For example, to map a first name and last name column to a full name object attribute, use a query like this: `“[%startobject%].firstname + ‘ ‘ + [%startobject%].lastname”`.
163+
{{% alert color="info" %}}
164+
Custom queries must be provided in the dialect of the database from which you are retrieving the data.
165+
{{% /alert %}}
166+
167+
For example, to map a first name and last name column to a full name object attribute, use a query like this: `[%startobject%].firstname || ' ' || [%startobject%].lastname`.
164168

165169
## Tab Page References
166170

0 commit comments

Comments
 (0)