2.9 Implementing Single Sign-On

Some sites use single sign‑on to allow users to log in once and access multiple software systems without having to log in multiple times. Single sign‑on can be used to bypass the need for logging in to Operations Center from the client. To achieve single sign-on, disable the Operations Center client login dialog box.

To disable logins to the Operations Center client, set the following parameters in the applet_params.xml file:

<param name="Client.DisableLogins" value="true" />
   <param name="Client.DisableLogins.AllowedAccounts" value="admin,guest" />
   <param name="Client.DisableLogins.Message" value="Access Denied" />


  • Client.DisableLogins disables logins to the operations client.

  • Client.DisableLogins.AllowedAccounts defines a comma separated list of accounts that should be allowed to log in. This would be applicable when the single sign‑on provider is not available and administrators still need to access the system.

  • Client.DisableLogins.Message is the message that displays to users when they are denied access.

For information on how to configure Single Sign On (SSO) for Operations Center databases, see Configuring and Administering the Database in the Operations Center Server Configuration Guide.

For single sign‑on options to use the auto-login function, or disable direct access to the dashboard server or operations client, see the Operations Center Dashboard Guide.