Migration overview

Infor has developed its own Security Token Service (STS) to handle all authentication needs for user access and application security within all Infor CloudSuites. This Infor STS replaces existing legacy security options.

Federations leveraging direct Infor CloudSuite IDP integration or Infor’s older STS Proxy mode must be updated to use Infor’s current Security Token Service (STS). Infor CloudSuite IDP (Ping Federate) and Infor STS Proxy modes are being deprecated and phased out. All federations must use Authenticate with InforSTS.

Note: Based on the requirements and the existing configuration of a customer’s identity provider, the instructions provided in this document may vary based on the assumptions in each of the sections below relating to federation.

Configuration must be completed through the Infor Federated Services (IFS) user interface. Infor OS provides the platform for administrators to configure. When the instructions are followed, customers can access the Infor OS multi-tenant application by using their organization credentials.

Customer configurations vary. This document is intended for best practices. The prerequisite knowledge required is an understanding of Single Sign On (SSO), IDP knowledge, and steps for customer setup.

Caution:

The Federated Identity configurations must be validated after creation. If not, there is a risk of unauthorized users gaining access to the system if the configurations are not done properly.

Contact your Customer Success Manager or open an Infor Support Incident for these items:

If assistance is required, there is an Infor team that can be engaged.
If there are other use cases not documented for the IDPs defined.
If customer configuration is complex and help is needed.