Requirements and Selection
There are four different deployment scenarios for the session providers:
-
AD FS 2.0+/PingFederate and Infor Federation Services
In this scenario, the users are authenticated to an identity provider using the SAML protocol. Infor Federation Services provides additional attributes and automation of the configuration. This scenario applies when Infor Ming.le™ is used.
-
Active Directory
In this scenario, Active Directory is used as the user information storage, but no identity provider (AD FS or PingFederate) is present. Users are authenticated directly to the AD.
-
Lawson Security
In this scenario, the SAML Session Provider is used together with the Identity Provider used for the Lawson Security System (Infor Lawson System Foundation or Infor Java Framework runtime environment).
-
Other LDAP
This scenario is for all other scenarios where users are stored in LDAP. The session provider authenticates the users directly to the LDAP server.
Choosing a Session Provider Based on the Scenario
An X in the matrix below means that the session provider supports the given scenario.
| Session Provider | AD FS 2.0+/PingFederate/IFS | Active Directory | Lawson Security | Other LDAP |
|---|---|---|---|---|
| Windows | -- X -- | |||
| LDAP | -- X -- | -- X -- | ||
| SAML | -- X -- | -- X -- |
Choosing which SAML Session Provider version to use
Infor ION Grid 11.1.13.0 supports two different versions of SAML Session Provider: 1.13.x and 1.14.x. The major difference between the versions is in which Infor Federated Services (IFS) version they support during deployment. Administrative tasks are the same during runtime.
SAML Session Provider 1.14 is built for deployment with InforOS and Infor XiPlatform. SAML Session Provider 1.13 is used to support IFS version 10.x and 11.x.
When deploying for Cloud using Ping Federate, use SAML Session Provider 1.13.