You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Zsombor Gegesy (JIRA)" <ji...@apache.org> on 2017/06/15 22:20:01 UTC
[jira] [Updated] (RANGER-1646) Error messages in RangerRESTClient
aren't helpful
[ https://issues.apache.org/jira/browse/RANGER-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zsombor Gegesy updated RANGER-1646:
-----------------------------------
Attachment: 0001-RANGER-1646-Instead-of-catching-the-errors.patch
> Error messages in RangerRESTClient aren't helpful
> -------------------------------------------------
>
> Key: RANGER-1646
> URL: https://issues.apache.org/jira/browse/RANGER-1646
> Project: Ranger
> Issue Type: Bug
> Components: plugins
> Affects Versions: 0.7.1
> Reporter: Zsombor Gegesy
> Assignee: Zsombor Gegesy
> Labels: exception-handling, plugins, ssl
> Fix For: 1.0.0
>
> Attachments: 0001-RANGER-1646-Instead-of-catching-the-errors.patch
>
>
> Currently, if the user accidentally configures the SSL settings incorrectly, or the keystore/truststore is not exists or not readable, then the user will receive a not too helpful 'SSLContext must not be null' coming from the com.sun.jersey.client.urlconnection.HTTPSProperties
> This happens, because RangerRESTClient.getKeyManagers / getTrustManagers / getSSLContext methods are catching the exceptions, and are returning null, instead of failing fast, so the user could easily act and fix the issues
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)