Configuring Tomcat for SSO

To use a standalone Deployment Automation installation with Release Manager, you must update configuration files to enable Serena Common Tomcat to find and use the correct SBM SSO installation.

Before you can use SSO with Deployment Automation, you must have SBM installed and SSO must be enabled. You must have the Deployment Automation server installed on the same machine as the Serena Common Tomcat.

On the Deployment Automation server, stop the Serena Common Tomcat service.
Navigate to the application server conf directory. For example: ..\Serena\..\common\tomcat\7.0\alfssogatekeeper\conf
In gatekeeper-core-config.xml, change the following parameters if necessary to replace the host and port values, shown here as [host] and [port], with the host and port for your SBM server.
- <parameter name="SecurityTokenService" Type="xsd:anyURI">HTTP://[host]:[port]/TokenService/services/Trust<parameter>
- <parameter name="SecurityTokenServiceExternal" Type="xsd:anyURI">HTTP://[host]:[port]/TokenService/services/Trust</parameter>
- <parameter name="FederationServerURL" Type="xsd:anyURI">HTTP://[host]:[port]/ALFSSOLogin/login</parameter>
Navigate to your program installation directory. For example: ..\Users\testauto\.serena\ra\conf\server

Modify the serena_ra_config.xml to set the ssoEnabled property to true as follows:

<ssoConfig>
    <ssoEnabled>true</ssoEnabled>
</ssoConfig>

On the Deployment Automation server, start the Serena Common Tomcat service.