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 does SBM connect to a SSL protected server
SBM has several Java-based components that can make calls to outside services that are protected with SSL. A few of these services are the Notification Server, Mail Client, Orchestration Engine and Application Repository. Orchestrations that use HTTPS SSL endpoints do so under the purview of the Orchestration Engine. When these services attempt to contact an SSL enabled endpoint (web service, Exchange Server, etc), it is required to tell the SBM JDK to trust the SSL certificate provide to it by the endpoint.
CMS-XML Using SourceBridge from the VM I-Net Web Client when the connection to the SBM server uses HTTPS (Secure Sockets Layer - SSL)
When the VM I-Net server (Serena VM Web Application Server) needs to talk to an SBM , TeamTrack or Tracker server using SSL (HTTPS), it is crucial that the Java Runtime Engine (JRE) used by Version Manager can verify the SSL certificate. This is not a problem when the certificate is a public one, obtained from the commercial Certificate Authorities (CA) Java knows about, but it can become problematic when the SSL certificate is either self-signed or signed by a non-public Certificate Authority.
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 How to remove the "The 'Serena Version Manager Server' certificate that is used by PVCS VM expires" message in SBM Configurator
Click on Security Change to the Secure Integrations tab From the "Select an integration" drop down list, select PVCS VM
CMS-XML SBM: Failed to contact Authentication Service at SERVERNAME with reason: Invalid User ID or Password
From the above mentioned KB: S139077 To secure SBM in a Distributed Server Installation: 1. Stop the IIS and JBoss services on your SBM servers.
CMS-XML Manually Configuring a Secure JBoss Cluster that Includes Single Sign-On (SSO)
On node 1, launch SBM Configurator and generate a new keypair for the STS, Federation Server, and SSO Gatekeeper. This secures node 1.
CMS-XML How to test whether JBoss or Tomcat is able to communicate with a https (secure) website.
Save the file TestHTTPS.class to an arbitrary directory on the SBM JBoss/Tomcat server. STEP 2:
CMS-XML Trying to test connection in Composer and get Connection attempt failed when "Use Secure Connection" is selected.
at Serena.Studio.Framework.Repository.AppRepositoryServiceRepository.TestConnection(String serviceURL, String authUser, String authPassword, Boolean useInternalSTSURL) at Serena.Studio.Framework.Repository.AppRepositoryServiceOptionsPanel2.btnTest_Click(Object sender, EventArgs e) For more information about using the JBOSS certificate supplied in versions of SBM 10.1.2+ see this doc. S138483
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)
To secure your installation, you must generate new key new key pairs. If you do not generate new key pairs, then the default certificates that the STS inherently trusts are used. To increase security you should generate a new unique certificate for each SSO component.
CMS-XML How to change the port number in scheduled reports URL from port 80 if using SSL on a secure port
If you are using SSL on port 443 or another secure port and the URL in scheduled reports email is showing port 80 and isn't working, go to the SBM Configurator under Mail Services> Notification Server> Link Settings> and verify that port 443 is listed. Restart all services in the SBM Configurator and the URL for scheduled reports will reflect port 443 when the email link is sent to the user.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs