Find Answers

Filter Search Results
All Products:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML SBM fails SSL if client certificate request is received from LDAP
SBM fails SSL if client certificate request is received from LDAP
CMS-XML Validation of SSL certificate that contains Alt Subject IP Names
Validation of SSL certificate that contains Alt Subject IP Names
CMS-XML SBM 11.1: Import or generate SSL certificate gives error "not part of the Windows Platform FIPS validated cryptographic algorithms"
SBM 11.1: Import or generate SSL certificate gives error "not part of the Windows Platform FIPS validated cryptographic algorithms"
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 Serena VM Web Application Server (Tomcat) SSL Sample Certificate Chain Contains RSA Keys Less Than 2048 bits
Serena VM Web Application Server (Tomcat) SSL Sample Certificate Chain Contains RSA Keys Less Than 2048 bits
CMS-XML VM 8.6.1: VM I-Net Web Client Agent cannot connect to server if IIS or Tomcat requires an SSL Client certificate
VM 8.6.1: VM I-Net Web Client Agent cannot connect to server if IIS or Tomcat requires an SSL Client certificate
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 Asynch Orchestration doesn't log a failure anywhere if using SSL with a certificate/connection problem to the Target Server
The logging you do get doesn't show a problem and it looks like the orch should have run but the event never makes it to the AlfEventManager log. We should either log this connection failure somewhere or at the least make the Test Connect button fail in the Repository when there is an SSL Connection issue. This Test Connect button should also pertain to Endpoints in the Endpoint area in Repository as well as the Target Servers area.
CMS-XML Configurator does not import IIS certificate chain
When importing an SSL certificate for IIS or JBoss/Tomcat, the intermediate CA (and possibly the root) does not get put into the certificate store.
CMS-XML Cannot connect Composer to IPv6 environment - invalid certificate
Connecting using Composer to an Application Repository using IPv6 throws an SSL certificate error. Composer cannot be connected - SSL certificate is invalid according to validation procedure.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs