Login Configuration (uigwt0002m000)
Use this page to determine how to log on to the LN UI.
This page contains these tabs:
- General
- On-prem Infor STS (IFS)
- MT Cloud Infor OS (Hybrid)
General tab
This tab contains general settings.
This table shows the fields in the General tab:
| Field | Description |
|---|---|
| HTTPS Port | If secure communication (HTTPS) is used
for LN UI access, specify the
communications port. Note: If the HTTPS port is changed, you must update
the HTTPS configuration. In addition, if STS
(IFS) is used, you must update the STS (IFS) configuration.
|
| Authentication Type | Depending on the Single Sign On type that is used, select On-prem Infor STS (IFS), MT Cloud Infor OS (Hybrid), or Integrated Windows Authentication. Otherwise select Backend, which requires users to provide their LN application server credentials when signing in. |
| Application URL | Specify the browser-facing URL of the LN UI web application that is used to generate the STS (IFS) configuration. This
URL also applies to clients of the LN Client Service. A non-default value
may be required if (browser) clients connect to the UI server using a load
balancer or reverse proxy. Click to change the Application URL to the default value. |
| Default Authentication Environment | This environment is used to authenticate the user if no default environment is specified in the user profile. |
| SAML2 Claim for User Identity | This field selects the SAML2 claim that is used to
identify the authenticated user. Supported values are:
Default, Identity2,
Email Address, User Principal
Name, Client Principal Name,
Identity (deprecated). The SAML2 claim that is applied if Default is selected depends on the selected Authentication Type:
|
| SAML2 Claim for User Display Name | This field selects the SAML2 claim that is used as the
display name of the authenticated user. Supported values are:
Default, None (User Display
Name equals User Identity), Common Name,
Identity2, Email Address,
User Principal Name, Client Principal
Name, Identity (deprecated). The SAML2 claim that is applied if Default is selected depends on the selected Authentication Type:
|
Within an SAML2 attribute statement, these attribute names are available for the supported SAML2 claim values:
- Identity2: http://schemas.infor.com/claims/Identity2
- Email Address: http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress
- User Principal Name: http://schemas.xmlsoap.org/ws/2005/05/identity/claims/upn
- Client Principal Name: http://schemas.infor.com/claims/ClientPrincipalName
- Common Name: http://schemas.xmlsoap.org/claims/CommonName
- Identity: http://schemas.infor.com/claims/Identity
On-prem Infor STS (IFS) tab
This tab contains the settings for the On-prem Infor STS (IFS) authentication type.
STS stands for Security Token Service. IFS stands for Infor Federation Services.
This table shows the fields in the On-prem Infor STS (IFS) tab:
| Field | Description |
|---|---|
| Configuration Web Service | Specify the URL of the Infor STS (IFS) configuration web service. |
| Relying Party ID | Identifies this Infor LN UI instance in Infor STS (IFS). The configuration web service generates the value. |
| WS-Trust URL | Identifies the WS-Trust URL, which may be used for the LN Client Service. |
| Token Signing Certificate valid until | Indicates the date until which the STS (IFS) configuration can be used to authenticate users. The Token Signing Certificate is part of the STS (IFS) configuration that is created using the Infor STS (IFS) configuration web service. |
| SHA-1 Thumbprint | Unique identification of the STS (IFS) token-signing certificate as found in the LN UI configuration. It must match the STS or AD/FS thumbprint. |
| STS (IFS) Configuration | Click to create the STS (IFS) configuration. If you click , the configuration web service starts and the Relying Party ID is retrieved. |
| Log | Shows progress information when the STS (IFS) configuration is created. |