Assigning An Identity Server To A Cluster Configuration; Configuring Session Failover - Novell ACCESS MANAGER 3.1 SP1 - IDENTITY SERVER Manual

11 After you configure the user store, the system displays the new configuration on the Servers
page.
The status icons for the configuration and the Identity Server should turn green. It might take several
seconds for the Identity Server to start and for the system to display a green light. If it does not, it is
likely that the Identity Server is not communicating with the user store you set up. Ensure that you
have entered the user store information correctly, and that you imported the SSL certificate to the
user store. (Edit > Local > [User Store Name].)

1.1.2 Assigning an Identity Server to a Cluster Configuration

After you create a configuration, you must assign an Identity Server to it. For clustering, you can
assign more than one Identity Server to the configuration (see
with Multiple Identity Servers," on page 21
any shared settings you have specified, such as attribute sets, user matching expressions, and custom
attributes that are defined for the server.
1 In the Administration Console, click Devices > Identity Servers.
2 On the Servers page, select the server's check box, then choose Actions > Assign to Cluster.
You can select all displayed servers by selecting the top-level Server check box.
3 Select the configuration's check box, then click Assign.
You are prompted to restart Tomcat. The status icon for the Identity Server should turn green. It
might take several seconds for the Identity Server to start and for the system to display the
green light.

1.1.3 Configuring Session Failover

When you set up an Identity Server cluster and add more than one Identity Server to the cluster, you
have set up fault tolerance. This ensures that if one of the Identity Servers goes down, users still
have access to your site because the remaining Identity Server can be used for authentication.
However, it doesn't provide session failover. If a user has authenticated to the failed Identity Server,
that user is prompted to authenticate and the session information is lost.
When you enable session failover and an Identity Server goes down, the user's session information
is preserved. Another peer server in the cluster re-creates the authoritative session information in the
background. The user is not required to log in again and experiences no interruption of services.
"Prerequisites" on page 20
"Configuring Session Failover" on page 20
"How Fallover Peers Are Selected" on page 20
Section 1.1.5, "Managing a Cluster
for the steps to set up a cluster). A configuration uses
Configuring an Identity Server 19