[
https://issues.apache.org/jira/browse/OOZIE-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13101733#comment-13101733
]
Hadoop QA commented on OOZIE-249:
---------------------------------
bansalmayank remarked:
Adding the Discussion thread....
I think that makes sense.
-Andreas.
On Feb 17, 2011, at 10:32 AM, Alejandro Abdelnur wrote:
On #2,
but why not have the credentials in the extension itself? For example:
<action name="myaction">
<authentication credentials="cred1,cred2" xmlns="uri:oozie:credentials">
...
</authentication>
<map-reduce> ... </map-reduce>
</action>
Thanks.
Alejandro
On Thu, Feb 17, 2011 at 12:55 PM, Angelo Kaichen Huang <[email protected]>
wrote:
On #1, you are right.
On #2, we have to let each action declare which credentials they need, we have
to something like that.
<action cred=”cred1, cred2”>
</action>
Therefore current schema has to be changed to add this attribute to action
element. That’s the reason for us to create a new schema instead of doing
extension.
Thanks,
Angelo
On 2/15/11 6:43 PM, "Alejandro Abdelnur" <[email protected]> wrote:
On #1, that info is in the action XML already, correct? if so you don't need to
store it again.
On #2, the WF schema does not care of what goes in the extension schema, so
changes in the extension schema do not affect the WF schema. That is the whole
point of using extensions. Regarding taking it later, once you go live with
this you'll have to support whatever schema changes you did, because of that I
think we should do this right from the get go.
Thanks.
Alejandro
On Wed, Feb 16, 2011 at 10:33 AM, Mayank Bansal <[email protected]> wrote:
Hi Alejandro,
We are not storing any credentials in the DB. Its just configuration like
server name etc.
For XML, In my understanding if we want to change anything in extension schema
we still need to refer that in workflow schema and that would change the
workflow schema as well. However its a good point and we can create an issue
and can take up later if its absolutely necessary.
Thanks,
Mayank
On 2/10/11 12:37 AM, "Alejandro Abdelnur" <[email protected]
<http://[email protected]> > wrote:
Mayank,
A couple of follow ups.
* Why do you need to store the credentials in the DB, they are in the action
XML, accessible?
* Why not use the WF XML extension points (like for SLA) instead modifying the
WF XML schema?
Thanks.
Alejandro
__._,_.___
Reply to sender | Reply to group | Reply via web post | Start a New Topic
Messages in this topic (16)
RECENT ACTIVITY: New Members 5
Visit Your Group
MARKETPLACE
Find useful articles and helpful tips on living with Fibromyalgia. Visit the
Fibromyalgia Zone today!
Stay on top of your group activity without leaving the page you're on - Get the
Yahoo! Toolbar now.
Switch to: Text-Only, Daily Digest • Unsubscribe • Terms of Use
.
> 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
