Verify the Truststore File for Metadata Manager Command Line Programs
Verify the Truststore File for Metadata Manager Command Line Programs
Effective in version 10.1, when you configure a secure connection for the Metadata Manager web application, the Metadata Manager command line programs do not accept security certificates that have errors. The property that controls whether a command line program can accept security certificates that have errors is removed.
The Security.Authentication.Level property in the MMCmdConfig.properties file controlled certificate validation for mmcmd or mmRepoCmd. You could set the property to one of the following values:
NO_AUTH. The command line program accepts the digital certificate, even if the certificate has errors.
FULL_AUTH. The command line program does not accept a security certificate that has errors.
The NO_AUTH setting is no longer valid. The command line programs now only accept security certificates that do not contain errors.
If a secure connection is configured for the Metadata Manager web application, and you previously set the Security.Authentication.Level property to NO_AUTH, you must now configure a truststore file. To configure mmcmd or mmRepoCmd to use a truststore file, edit the MMCmdConfig.properties file that is associated with mmcmd or mmRepoCmd. Set the TrustStore.Path property to the path and file name of the truststore file.
For more information about the MMCmdConfig.properties files for mmcmd and mmRepoCmd, see the
