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 Web Browser complains the SSL certificate has expired, even though the expiration date is in the future.
Web Browser complains the SSL certificate has expired, even though the expiration date is in the future.
CMS-XML RLC: Creating task template from Release Package, get error "Unsafe SSL is not allowed. Client certificate doesn't needed. Couldn't connect."
RLC: Creating task template from Release Package, get error "Unsafe SSL is not allowed. Client certificate doesn't needed. Couldn't connect."
CMS-XML SBM SSO SSL Integration with Version Manager - Configurator will not take certificate
Once a self signed certificate is added to the Security - SSL Integrations section in configurator you can not over write it again later using Configurator.
CMS-XML How to install the SBM certificate into the ZMF Connector (ALM Connector) java keystore
This article goes through the steps to import a certificate into the Java Keystore ( cacerts ) file so JBoss can communicate via SSL / HTTPS to secure sites and URL's. You first need to acquire the public certificate or DER encoded binary X.509 (.CER) file to import. For more information on this see KB S139798
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 RLC Web Service/Orch fails with error "The https URL hostname does not match the Common Name (CN) on the server certificate in the client's truststore."
This problem can occur when SBM is setup to use load balancing and SSL communication. In the common log, you will see errors like this:
CMS-XML RLC Web Service/Orch fails with error "The https URL hostname does not match the Common Name (CN) on the server certificate in the client's truststore."
This problem can occur when SBM is setup to use an internal and external host name and SSL communication. In the common log, you will see errors like this:
CMS-XML RLC: Error "PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target" when not using SSL
This error is typically associated with SSL certificates (see KB S139798 ). However, in this situation, the user was not running SSL.
CMS-XML How to fix a 404 error when using the Rest Grid widget with an SSL (HTTPS) url. "We did not find any matches for your request"
We did not find any matches for your request Unknown error received from https....... The attached video goes through the steps to make sure JBoss / Tomcat has the appropriate ssl certificate so a trusted connection can be made and the results displayed.
CMS-XML How to configure one-way and two-way SSL for Release Control and ZMF Connector
1. Obtain a Certificate Authority (CA) root certificate and generated keypair certificates for the SBM hostname and the ZMF Connector hostname, signed by the CA root certificate . SBM should be configured to use one-way SSL with these certificates. Refer to the SBM documentation on Documentation Center or from the SBM interface, especially the SBM Configurator Help.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs