Sure. I'll open a JIRA and I'll include the detailed logs from xa_portal.log. I have noticed that the policies I've created for Knox work perfectly. The ranger admin just can't lookup topology information for autofilling on the policy creation screens. Not tragic, but definitely functionality that would be nice.
Sent from my iPhone On Mar 31, 2015, at 4:25 PM, Balaji Ganesan <[email protected]<mailto:[email protected]>> wrote: We should look into that. Can you create a JIRA on this? Note that repository connection for resource name look up from the policy manager. You can still save the repository and start creating policies. On Tue, Mar 31, 2015 at 11:18 AM, Rich Haase <[email protected]<mailto:[email protected]>> wrote: Could someone please explain to me the cause of this error? I’m assuming this is some sort of simple configuration mistake on my part, but I’ve not been able to find any documentation that explains the SSL setup sufficiently. ====== Connection Failed. Exception on REST call to KnoxUrl : https://<host>:8443/gateway/admin/api/v1/topologies. You can still save the repository and start creating policies, but you would not be able to use autocomplete for resource names. Check xa_portal.log for more info. javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No name matching <host> found. java.security.cert.CertificateException: No name matching <host> found. No name matching <host> found. ===== I’ve replaced "<host>" with the actual hostname in the error messages. Thanks, Rich
