[
https://issues.apache.org/jira/browse/OOZIE-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13101737#comment-13101737
]
Hadoop QA commented on OOZIE-249:
---------------------------------
tucu00 remarked:
Extensions were added to allow users to annotate their WF with additional
information Oozie does not care about.
SLA handling was a one off as it was special (Oozie had to do something). With
Authentication the same thing happens.
You are correct, Oozie does not have an API to handle extensions.
I think a cleaner way is to add an API to handle extensions.
And yes, all actions should be extensions as they evolve much faster than the
WF itself.
> GH-332: Authentication module for oozie
> ---------------------------------------
>
> Key: OOZIE-249
> URL: https://issues.apache.org/jira/browse/OOZIE-249
> Project: Oozie
> Issue Type: Bug
> Reporter: Hadoop QA
>
> As Oozie is the workflow engine on the gateway, it has to be integrated with
> all other grid systems in order to run jobs and compliant with their
> authentication policy. Oozie should authenticate those users and propagate
> credentials (i.e delegation tokens) to the tasks through job conf by that
> they can be used by the tasks to authenticate themselves against those
> systems while running.
> We need one unified interface for user by which they can specify what all the
> systems they want to use and authenticate against and should be able to
> provide configuration for authentication.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
