You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Robert Levas (JIRA)" <ji...@apache.org> on 2018/02/28 15:16:00 UTC
[jira] [Commented] (AMBARI-23106) Use localjceks URL for credential
provider for local files
[ https://issues.apache.org/jira/browse/AMBARI-23106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16380450#comment-16380450 ]
Robert Levas commented on AMBARI-23106:
---------------------------------------
[~zsombor], The issue you are trying to solve is unclear. Can you add more details?
From what I gather, the path to the keystore used by the Hadoop Credential Provider is set, by default, to be in HDFS. This is done by specifying {{jceks}} as the protocol in the file URL. However there is some scenario where access to HDFS is not available/allowed and therefore the keytstore needs to be stored in the local file system, which can be achieved by setting the protocol to {{localjceks}}.
Is this problem local to Oozie?
Is there information that can be used by Ambari to determine which filesystem to choose? Or maybe this should be a configuration?
> Use localjceks URL for credential provider for local files
> ----------------------------------------------------------
>
> Key: AMBARI-23106
> URL: https://issues.apache.org/jira/browse/AMBARI-23106
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
> Affects Versions: 2.6.0
> Reporter: Zsombor Gegesy
> Priority: Major
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Ambari generates 'jceks://file/\{filepath}' as a credential provider URL, which force using the JavaKeyStoreProvider - which uses the hdfs API to access the local file system.
> This cause problems, when the local file system access from that API is disabled - for security reasons, for example in Oozie. Fortunately, there is a LocalJavaKeyStoreProvider which can be used in this case, which can be accessed with a 'localjceks://file/\{filepath}' URL
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)