Configuring Single Sign On

The Single Sign On (SSO) authentication method permits Users to access pages in AlarmPoint directly without first logging in via the Sign In page. This method uses an external authentication module, and supplies an authentication string to AlarmPoint.

Note: AlarmPoint does not currently support SSO with AlarmPoint OnDemand or Enterprise deployments with multiple Companies.

To use SSO authentication, the following criteria must be met:

The HTTP headers must contain the following three lines:

HTTP_SM_AUTHENTIC = “YES”
HTTP_SM_AUTHORIZED = “YES”
HTTP_SM_USER = “<User web login ID>”
Note: The “HTTP_” portion of the header lines is optional, but all three lines must use the same convention.

When the criteria have been met, Users can directly access any page that is normally accessed via the main AlarmPoint menus on the left side of the screen. For example, a User authenticated with SSO can navigate directly to their Active Alerts page using the following URL:

<AlarmPointIP>/alarmpoint/Alerts/ActiveAlerts/ActiveAlerts.do

Note that the semi-colon and the session information that follows in the URL shown in your browser is not included in the URL initially used to load a page using SSO.

To reach the Sign In page and log in to AlarmPoint as a different User when an SSO deployment portal is in place, click the Sign Out link at the top of any page. You can then sign in using any authorized AlarmPoint web login ID and password.

AlarmPoint also redirects to the default Sign In page in any of the following circumstances:

If the User authenticated by SSO does not have permission to view the page specified in the URL, AlarmPoint redirects them to a standard access denied page. If the User accesses AlarmPoint through the default URL, AlarmPoint redirects them automatically to their home page.

Configuring SSO header variable names

By default, AlarmPoint is configured to use SiteMinder Web Access Manager SSO header; i.e., SM_AUTHENTIC, SM_AUTHORIZED, SM_USER. You can modify these SSO headers by adding code to the web.xml configuration file and editing it as required.

To change the SSO header variables:
  1. Navigate to the <Webserver-Install-Directory>/webapps/cocoon/WEB-INF/ folder and open the web.xml file in an editor.
  2. Locate the WebAuthenticationFilterProxy tag.
  3. Below the existing <init-param> name-value pair nodes, add three new nodes with the following names: authenticateHeader, authorizedHeader, and userHeader; for example, the default configuration is:
  <filter>
   <filter-name>WebAuthenticationFilterProxy</filter-name>
        ...
    <init-param>
      <param-name>authenticateHeader</param-name>
      <param-value>SM_AUTHENTIC</param-value>
    </init-param>
    <init-param>
      <param-name>authorizedHeader</param-name>
      <param-value>SM_AUTHORIZED</param-value>
    </init-param>
    <init-param>
      <param-name>userHeader</param-name>
      <param-value>SM_USER</param-value>
    </init-param>
  </filter>
  1. Modify the param-value entries as necessary and save the web.xml file.
  2. Restart the web server.
Note: These steps must be carried out on all web servers in your AlarmPoint deployment.