Integration → Integrating with SBM → Single Sign-On (SSO) Configuration → Configuring Tomcat for SSO
To use a typical Deployment Automation installation with SBM, 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.
<parameter name="SecurityTokenService" Type="xsd:anyURI"> HTTPS://myserver:8243/TokenService/services/ Trust<parameter> <parameter name="SecurityTokenServiceExternal" Type="xsd:anyURI"> HTTPS://myserver:8243/TokenService/services/ Trust</parameter> <parameter name="FederationServerURL" Type="xsd:anyURI"> HTTPS://myserver:8243/ALFSSOLogin/login </parameter>
<ssoConfig> <ssoEnabled>true</ssoEnabled> </ssoConfig>
ALF SSO Gatekeeper error has occurred: Error obtaining security token.
Validation of WS-Federation token failed with code 40:Token issuer not allowed.
See the Serena Knowledgebase item S140637 for more information.
If you upgrade Deployment Automation from a version that uses Tomcat 7 to one that uses Tomcat 8, you must perform the steps in Configuring Tomcat for SSO again, including setting the parameters in the gatekeeper-core-config.xml file.
Set these parameters by copying over the corresponding strings from the old gatekeeper-core-config.xml file. Copying and replacing the entire file from the old Tomcat installation does not work.
Copyright © 2011–2016 Serena Software, Inc. All rights reserved.