Simplified SMS architecture using an authentication provider

This system design contains a minimum of two nodes for user authentication, and provides robustness and redundancy.

Node 1 - SMS on the GR or other deployed platform

In this simplified architecture, the System Management Server is installed on the GR node.

• On the System Management Server tab of the Configurator, select the option "This machine is the System Management Server."

• On the Authentication Provider tab:

  • Select the checkbox to "Configure this machine to provide SSO via an external Authentication Provider."

  • Configure the token host.

Node 2 - redundant SSO node on the IDE

The System Management Server is installed on an IDE node or an Application Object Server (run-time) node.

• On the System Management Server tab of the Configurator, select the option "Connect to an existing System Management Server."

  • Select node 1 as the existing SMS node.

  • Select the checkbox "Configure this machine as a Redundant SSO Server."

• On the Authentication Provider tab:

  • Select the checkbox to "Configure this machine to provide SSO via an external Authentication Provider."

  • Configure the token host.

Node 2 is now configured as a redundant authentication provider.

Node 3 though n

• On the System Management Server tab of the Configurator, select the option "Connect to an existing System Management Server."

  • Select node 1 as the existing SMS node.

  • For the option to configure the node as a Redundant SSO Server, leave the checkbox unchecked.

• On the Authentication Provider tab:

  • Select the checkbox to "Configure this machine to provide SSO via an external Authentication Provider."

    Note: Since this node is not a redundant authentication provider, the fields to configure a token host are not shown.