Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created 01-30-2017 04:43 PM
Hello,
After rolling out SSL to the Ranger Admin Page, I noticed my policy changes weren't syncing with the name nodes. I found I needed to setup the plugin for SSL. I followed these procedures (https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.5.0/bk_security/content/ch04s19s02s04s01.html) and had nothing. After looking at the namenode logs I see the error message saying:
com.sun.jersey.api.client.ClientHandlerException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: No trusted certificate found at com.sun.jersey.client.urlconnection.URLConnectionClientHandler.handle(URLConnectionClientHandler.java:149)
I am not quite sure where else to look.
Nick
Created 01-30-2017 05:38 PM
Yes, you will have to put the Ranger Cert into HDFS truststore,. also by default it enables 2 way SSL between Ranger admin and HDFS plug-in.
Some time back I have written article here with complete steps.
Created 01-30-2017 05:38 PM
Yes, you will have to put the Ranger Cert into HDFS truststore,. also by default it enables 2 way SSL between Ranger admin and HDFS plug-in.
Some time back I have written article here with complete steps.
Created 01-30-2017 06:19 PM
If you enable SSL on ranger, you need to update the truststore.
Please refer http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.5.3/bk_security/content/configure_ambari_ranger_...
Created 01-30-2017 06:25 PM
@apappu
That was the hint I needed. It appears I had a keystore set for my HDFS ranger truststore. So no matter what I did, I would be unable to fix it. Once I corrected that issue, I see my namenode pulling the policy. Glad it was something stupid.
Nick