Description
Currently if no truststore is specified, the Ranger SSL code path will refuse to connect, giving an error message "TrustManager is not specified".
Specifying a trust store should not be necessary if the ranger server has its cert signed by a CA that is already trusted by the JVM, for example because the cert is signed by a public CA, or a private CA cert has been put into the default JVM trust store, or because it has been configured via Java system properties on the command line.
Attachments
Issue Links
- duplicates
-
RANGER-2907 Ranger Plugin is not using default TrustManager if a trustmanager is not specified in ranger-policymgr-ssl.xml
-
- Resolved
-