With VM 8.6.0 and older, the Java plug-in would use the network connection that was already established by the browser. If the server was configured to require an SSL Client certificate , but the browser had this certificate , the Java applet would therefore transparently be allowed access.
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.
This error indicates the SSL certificate from the SBM server was signed by a Certificate Authority (CA) not known to the Java Runtime Engine (JRE) being used by the RIDE client. This is common when the certificate was signed by an internal CA as opposed to one of the well-known external ones (VeriSign, DigiCert, etc.).
You can create a certificate database with the Mozilla Certutil utility. Certificate databases are platform independent and can be used across multiple operating systems.
Exception: System.Security.Authentication.AuthenticationException Message: The remote certificate is invalid according to the validation procedure. Source: System
Users of VM 8.6.2 or newer should go to step 2. Delete the file vm\common\tomcat\ conf \serena.keystore On Windows this can be done by executing the command:
All of the following commands are executed from the directory VM_Install_Dir \vm\common\tomcat\ conf (e.g. C:\Program Files (x86)\Serena\vm\common\tomcat\conf
CRL File -> C:\Users\rgering\serena.crl CA Alias -> serena sample ca CA Keystore -> C:\Program Files (x86)\Serena\vm\common\tomcat\ conf \serena-ca.keystore
