Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML Configuring SSO Protected Hosts
Configuring SSO Protected Hosts
CMS-XML SSO protected hosts - 403 Error – Forbidden
SSO protected hosts - 403 Error – Forbidden
CMS-XML VM I-Net Web Client login fails with HTTP ERROR 403 for servlets using an SBM SSO server for authentication
The security enhancement restricts access to the SSO Login web page to a list of authorized servers, which by default consists of just the SBM server itself. To use PVCS VM with this SSO server , the DNS name of the VM server has to be added to the SSO Protected Hosts
CMS-XML Manually Configuring a Secure JBoss Cluster that Includes Single Sign-On (SSO)
4) Import the snapshot configuration file on the machine that hosts the Application Engine. 5)
CMS-XML Clustering JBoss with SSO Enabled and Securing Your Load Balancer
If you configure your JBoss load balancer to use HTTPS, in order for users to access SBM in a clustered environment in which SSO is enabled, you must manually update the following files on the SSO server : SBMInstallDirectory \Serena\SBM\Common\jboss405\server\all\deploy\ALFSSOLogin.war\WEB-INF\conf\ fedsvr-core-config.xml
CMS-XML Configurator gives error "Unable to configure gatekeeper-core-config.xml. This may affect normal functioning of Single Sign-On features." and can't set overrides in Secure SSO section.
This error was caused by a change that was made to the following file outside of configurator. C:\Program Files\Serena\SBM\Common\Tomcat 7.0\ server \default\webapps\idp\WEB-INF\conf\Configuration.xml In this case there was a section remarked out by the customer and was causing configurator to not be able to update the override section which in turned caused the gatekeeper-core-config.xml file to not get the override set.
CMS-XML SSO and SSL: Only secure content is displayed and users get error about mixed content
In Configurator, on the Component Server view, for the Application Engine (AE) component, uncheck the HTTP option so only the HTTPS option is checked. However, for this to work correctly, the AE host name must also match the "Issued To" name of the certificate in Configurator on the IIS Server view.
CMS-XML 10.1-10.1.1.3 (Earlier versions affected if SSO On) - SBM Sample Certificates for STS, Federation Server and SSO Gatekeeper expire on 13th June 2015 or 16th September 2017 - Error message: Failed to verify signature
SBM 10.1 - 10.1.1.3 To secure SBM in a Single Server Installation: 1. Stop the IIS and JBoss services on your SBM server.
CMS-XML SBM 10.1.1.4+ and SBM 11.x: How to generate new signed certificate trust keys for SBM and copy them to additional servers as needed (Generating SSO certificates)
Open Configurator, and go to Security. On the Secure SBM tab, click "Generate All" Apply the changes.
CMS-XML SBM 10.1 - 10.1.1.3: How to generate new signed certificate trust keys for SBM and copy them to additional servers as needed (Generating SSO certificates)
The following note in the SBM Installation and Configuration Guide recommends that you generate new key pairs to secure your installation: Important:
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs