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 12.2.0.3 / connection to ldaps is failing / OpenSSL error error:140940E5:SSL routines:SSL3_READ_BYTES:ssl handshake failure
t1cb8 IO bf16:4d ### ERR handle EIOSSLREAD 4cc58 10.194.0.35:15259 ukwn Trouble processing events for fd=314456 (e.g. i/o error). Will drop connection. ( accept from 4100 (3))
CMS-XML Using SourceBridge from the VM I-Net Web Client when the connection to the SBM server uses HTTPS (Secure Sockets Layer - SSL)
If you would like, you can use the attached Java application TestHTTPS to verify that the JRE keystore now accepts the HTTPS-based URL for the SBM / TeamTrack / Tracker server . To run the application, save the file TestHTTPS.class
CMS-XML Get Internal Server Error (500) when logging into the Application Repository.
Both of these errors indicate some kind of communication problem with JBoss and the database server. In this case the MSSQL server was setup to only accept SSL communication which doesn't cause a problem for the Application Engine database since it uses ODBC and is able to negotiate SSL connections automatically but did become a problem for the other databases that communicate via JDBC like the Repository, Common Log and Orchestration Engine databases. If this appears to be the case in your situation look at this KB S139719 doc for steps on how to remedy.
CMS-XML How to ignore erroneous SSL with LDAP errors when certificate appears correct. (Certificate common name does not match the host )
There may be a situation where the ssl certificate being used to make a secure LDAP connection appears to be valid by all accounts yet the test connect still won't work. ... Certificate common name does not match the host ldap.usa.dce.us.gov : error 'Neither subjectAltName extensions nor commonName match' : 0x800b010f ... To avoid the situation when old certificates might not be accepted after WinLDAP adoption by SBM, the mechanism to ignore specific certificate validation errors is provided.
CMS-XML How to enable SBM to communicate via SSL with a SQL Server database
... Set the JDBC connection string correctly ... set the JDBC connection string to connect ... SQL Server using SSL . ... the Windows ODBC connection will automatically negotiate to use SSL therefore you do ... ... your SQL Server SSL certificate into the ... ... either "; ssl =require ... or "; ssl =request ... You have to accept the red error ... you test the connection 'no such ... ... the "; ssl =required" ... your SQL Server SSL certificate chain into ... ... use "; ssl =authenticate ... on the JBoss server . ... jboss405\ server \default\ ...
CMS-XML How to enable SBM to communicate via SSL with a SQL Server database in SBM 11.x
... Set the JDBC connection string correctly ... set the JDBC connection string to connect ... SQL Server using SSL . ... the Windows ODBC connection will automatically negotiate to use SSL therefore you do ... ... your SQL Server SSL certificate into the ... ... select "Use SSL " on the ... ... either "; ssl =required" ... or "; ssl =requested" ... You have to accept the red error ... you test the connection 'no such ... ... the "; ssl =required" ... your SQL Server SSL certificate chain into ... ... use "; ssl =authenticate ... on the Tomcat server .
CMS-XML How to set up SSL with Portfolio Edge
SSL Certificates can be ... ... cases where the SSL client side of ... the choice of accepting or rejecting that ... This works properly for PE in these cases where the SSL connection is initiated from the user interface. PE also contains cases where the server initiates its own SSL connections to other servers or itself. ... Therefore, it is critical to proper server operation that the chain of trust for the issuing certificate authority be established at minimum on the server system(s) for those systems to which it may be initiating requests.
CMS-XML DimCM: Desktop Client: The request to Dimensions CM Pulse was not successful. SSL peer certificate or SSH remote key was not OK
The above error only occurs when you are using SSL or HTTPS with Dimensions CM and Pulse AND within the Desktop Client. To fix ... 1. Verify what certificates the $DM_ROOT\cm\dfs\cacerts.pem file has within it.
CMS-XML How does SBM connect to a SSL protected server
javax.mail.MessagingException: Error while RETRIEVING ITEMS FROM MS_EXCHANGE. Please check Configurator connection parameters.;
CMS-XML Restricting Oracle Connections to Client10 or Higher
The “Oracle for SBM” driver was upgraded to version 07.10.0030 in SBM 10.1.3. The 07.10.0030 driver is configured to connect to the Oracle server using Client10, which enables connection to the Oracle server over SSL (not available in Client8 or Client9).
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs