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 How to setup SSO to validate users with LDAP, instead of SBM Application Engine validating the users with LDAP
How to setup SSO to validate users with LDAP, instead of SBM Application Engine validating the users with LDAP
CMS-XML RM client installation doesn't show dialog for the SSO settings setup
Remote Import client does not reflect SSO settings.
CMS-XML How to setup Dimensions CM, RM and other Serena products to utilize the SBM SSO using LDAP authentication model
Goal: To enable SSO enabled product to login using SBM SSO without requiring the user to exist in the SBM database.
CMS-XML Warnings in SSO log files in clustered setup - Creating a new instance of CacheManager using the diskStorePath - Configuring ehcache from ehcache-failsafe.xml found in the classpath
Warnings in SSO log files in clustered setup - Creating a new instance of CacheManager using the diskStorePath - Configuring ehcache from ehcache-failsafe.xml found in the classpath
CMS-XML How to setup RLM (Release Automation, SDA, SRA) to use SSO with SBM
This document assumes that SBM and RLM are already installed and running. This document only covers how to setup SSO .
CMS-XML Serena SSO/CAC Setup through port 443 Only
When enabling SSO /CAC with port 443 only, we will need to redirect calls to get the client certificate through IIS and the SBMConnector
CMS-XML Configurator does not always completely configure all files when External Filters used with SSO
If you are having problems using SBM web-services and you have setup SSO to use External Filters, then it is possible there is more manual configuration required. If you have External Filters defined in SSO and are having problems with Web Services, then contact Support
CMS-XML Configurator does not allow for setting up SSO for external identity provider while using non-SSO auth on local server
Configurator removes the "custom HTTP header" or "remoteuserheader" setting from the web.xml whenever the authentication is changed (even with the "override authentication settings for this server" checked) away from the external identity provider with SSO. This prevents the setup of SSO using an external identity provider being used while using a non- SSO form of authentication on the local JBoss server where SSO is installed without manually modifying the web.xml file.
CMS-XML Configuring SSO Protected Hosts
Configuring SSO Protected Hosts
CMS-XML SRA: Configuring SSO documentation correction
SRA: Configuring SSO documentation correction
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs