The file-based trust manager provider determines whether to trust a presented certificate based on whether that certificate exists in a server trust store file. The trust store file can be in either JKS (the default Java key store format) or PKCS#12 (a standard certificate format) form. 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 can be an absolute path or a path that is relative to the instance root. Changes to this configuration attribute take effect the next time that the trust manager is accessed. .* STRING An absolute path or a path that is relative to the directory server instance root. 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 always include 'JKS' and 'PKCS12', but different implementations can allow other values as well. If no value is provided, then the JVM default value is used. Changes to this configuration attribute take effect the next time that the trust manager is accessed. .* STRING Any key store format supported by the Java runtime environment. The "JKS" and "PKCS12" formats are typically available in Java environments. ds-cfg-trust-store-type