Table of Contents


  1. Preface
  2. Part 1: Version 10.4.1
  3. Part 2: Version 10.4.0
  4. Part 3: Version 10.2.2
  5. Part 4: Version 10.2.1
  6. Part 5: Version 10.2
  7. Part 6: Version 10.1.1
  8. Part 7: Version 10.1

Verify the Truststore File for Command Line Programs

Verify the Truststore File for 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. This feature is also available in 9.6.1 HotFix 4. It is not available in 10.0.
The Security.Authentication.Level property in the 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 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 files for mmcmd and mmRepoCmd, see the "Metadata Manager Command Line Programs" chapter in the
Informatica 10.1 Metadata Manager Administrator Guide


We’d like to hear from you!