| |
Results |
|
TRKInet: How to change the Sample.html to use SSL links
|
By default the Tracker Inet Configuration tool is setup to generate sample.html links to use http://<servername> base URL.
|
|
|
|
Two-way SSL configuration for Manual Deployment Tasks
|
check boxes. Under Link Settings /Web server
|
|
|
|
Composer cannot connect to the Repository - Error: ... Failed to retrieve valid security token ... could not establish trust relationship for the SSL/TLS secure channel with authority
|
If you are not using SSL then in Configurator deselecct the SSL configuration for Tomcat. Untick "Use HTTPS on Port" and Apply.
|
|
|
|
The dmpasswd for setting SSL passwords does not work sometimes as mentioned
|
The DIM CM2009 R2 Administrator's Guide (Configuring Dimensions CM to Run SSL Encrypted Network Connections section). The guide contains the following command line to set SSL password
|
|
|
|
Meritage -Meritage fails when Tomcat is configured to accept SSL connections only.
|
The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. Additionally, in .\Documents and Settings \<User_ID>\Application Data\Serena\Meritage\meritage.log the following will be found: 2005-07-12 11:54:18,777 [3908] INFO Merant.DocShare.UI.Forms.ServerSetupForm - The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
|
|
|
|
This page can’t be displayed. Turn on TLS 1.0, TLS 1.1, and TLS 1.2 in Advanced settings and try connecting to https://servername again.
|
An error of "This page can’t be displayed. Turn on TLS 1.0, TLS 1.1, and TLS 1.2 in Advanced settings and try connecting to https://servername again." in the web browser can be caused by an incorrectly imported SSL certificate or missing intermediate or root certificates.
|
|
|
|
SSL Configuration for Portfolio Edge and Mariner
|
9. Check the gUse secure connection h checkbox.
|
|
|
|
local connect mode doesn't work with SDP over SSL configured in CM Server
|
The result for this configuration end in the below error: Actual result: > export DMDB=cm_typical@ora11
|
|
|
|
After upgrading to VM 8.6.1 or newer, HTTPS connections to the File Server may fail with SSL routines:ssl3_get_server_certificate:certificate verify failed
|
In the default configuration that means neither self-signed certificates, nor certificates signed by an internal CA, are accepted anymore. Internal Certificate Authorities can
|
|
|
|
DimCM: Git Connector: com.serena.dmclient.api.DimensionsRuntimeException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed:
|
To fix this issue you will need to have the Server's public certificate, either signed or self-signed, and it's chain of certificates added to the Git Connector's JRE directory. For instance, When we tested Git Connector in this configuration , we used a self signed certificate for the server and copied its public cert to the client and then ran:
|
|
|
