pcli run -sKeyTool.pcli will provide usage on how to run the script and provide additional examples. To update the certificates without using this script, execute the following commands:
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.). To solve this error, the list of approved Certificate Authorities used by the JRE needs to be updated .
To create a unique certificate for the default keystore, you can execute the following certtool commands. Note that certtool needs to update files in the VM installation directory, so it needs to be executed by a user with sufficient privileges. On Windows, run certtool from a Command Prompt (CMD.EXE) that was launched using right-click | Run as administrator.
As certtool needs to update files in the VM installation directory, execute it as a user with sufficient privileges. On Windows, run certtool from a Command Prompt (CMD.EXE) that was launched using right-click | Run as administrator
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 VM Server. 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.).
The certificate path is kept as merant\vm\common\bin\win32 instead of serena\vm\common\bin\win32 ... Reconfigure LDAP in Version Manager or manually update the ldapinfofile as follows:
