The provider accesses key information in a file on the local filesystem. Multiple file formats may be supported, depending on the providers supported by the underlying Java runtime. ds-cfg-file-based-trust-manager-provider ds-cfg-trust-manager-provider org.opends.server.extensions.FileBasedTrustManagerProvider Should use a file-based property definition? Specifies the path to the file containing the trust information. It may be an absolute path, or a path that is relative to the instance root. Changes to this configuration attribute will take effect the next time that the trust manager is accessed. ds-cfg-trust-store-file Can we restrict this to an enumeration? How can the client guess which values are possible? What is the default value? Specifies the format for the data in the trust store file. Valid values should always include 'JKS' and 'PKCS12', but different implementations may allow other values as well. If no value is provided, then the JVM-default value will be used. Changes to this configuration attribute will take effect the next time that the trust manager is accessed. ds-cfg-trust-store-type