[
https://issues.apache.org/jira/browse/OOZIE-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter resolved OOZIE-2823.
----------------------------------
Resolution: Won't Fix
Oozie has no control over this, it's due to the way credstore passwords are
read in and the NodeManager. In any case, I believe the password file property
should work in an Oozie Action in Hadoop 2.7.3 or later.
> hadoop.security.credstore.java-keystore-provider.password-file is ignored by
> Oozie Sqoop actions when using the password-alias option with a passworded
> keystore.
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: OOZIE-2823
> URL: https://issues.apache.org/jira/browse/OOZIE-2823
> Project: Oozie
> Issue Type: Improvement
> Components: action
> Reporter: Thomas Scott
> Priority: Minor
>
> The --password-alias option in Sqoop allows you to retrieve the password for
> a connection from a keystore.
> As per
> https://hadoop.apache.org/docs/r3.0.0-alpha1/hadoop-project-dist/hadoop-common/CredentialProviderAPI.html
> this keystore can also have a password and this can be stored in a file
> using the hadoop.security.credstore.java-keystore-provider.password-file
> option
> Oozie doesn't currently seem to support this and instead we use the
> workaround:
> <property>
> <name>oozie.launcher.mapred.map.child.env</name>
> <value>HADOOP_CREDSTORE_PASSWORD=`cat some_password_file`</value>
> </property>
> Oozie Sqoop actions should support the neater
> hadoop.security.credstore.java-keystore-provider.password-file method.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
