You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Robert Kanter (JIRA)" <ji...@apache.org> on 2015/01/06 19:36:35 UTC
[jira] [Updated] (OOZIE-1458) If a Credentials type is not defined,
Oozie should say something
[ https://issues.apache.org/jira/browse/OOZIE-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Kanter updated OOZIE-1458:
---------------------------------
Fix Version/s: 4.1.0
> If a Credentials type is not defined, Oozie should say something
> ----------------------------------------------------------------
>
> Key: OOZIE-1458
> URL: https://issues.apache.org/jira/browse/OOZIE-1458
> Project: Oozie
> Issue Type: Improvement
> Components: security
> Affects Versions: trunk
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Fix For: 4.1.0
>
> Attachments: OOZIE-1458.patch
>
>
> If you use the Credentials Module and define a {{<credentials>}} section like this:
> {code:xml}
> <credentials>
> <credential name='woot' type='hcat'>
> <property>
> ...
> </property>
> </credential>
> </credentials>
> {code}
> but you didn't add a credentials type for {{hcat}} in oozie-site.xml; that is, you *did not* add this:
> {code:xml}
> <property>
> <name>oozie.credentials.credentialclasses</name>
> <value>hcat=org.apache.oozie.action.hadoop.HCatCredentials</value>
> </property>
> {code}
> then Oozie will silently not use the credentials class (because it doesn't know about it) so the action trying to use it will fail. It's pretty easy to forget to add the property to oozie-site.xml, so it would be nice if instead of silently ignoring needing to acquire a credential for an action, the workflow should fail either on that action when it tries to use the credential and can't find it, or (probably better) when submitting the workflow as part of the initial checking (e.g. after we do the forkjoin checking or something).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)