You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Purshotam Shah (JIRA)" <ji...@apache.org> on 2014/11/25 21:33:13 UTC
[jira] [Updated] (OOZIE-1688) New configuration to specify
server-server authentication type.
[ https://issues.apache.org/jira/browse/OOZIE-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Purshotam Shah updated OOZIE-1688:
----------------------------------
Attachment: OOZIE-1688-V6.patch
> New configuration to specify server-server authentication type.
> ---------------------------------------------------------------
>
> Key: OOZIE-1688
> URL: https://issues.apache.org/jira/browse/OOZIE-1688
> Project: Oozie
> Issue Type: Bug
> Components: HA
> Reporter: Purshotam Shah
> Assignee: Purshotam Shah
> Attachments: OOZIE-1688-V4.patch, OOZIE-1688-V5.patch, OOZIE-1688-V6.patch, OOZIE-1688-v1.patch, OOZIE-1688-v1.patch, OOZIE-1688-v2.patch, OOZIE-1688-v3.patch, OOZIE-1688.patch
>
>
> Currently conf "oozie.authentication.type" is used by specify authentication type for client-server as well as server-server.
> Client-server and server-server communication can use different type of authentication.
> We need to have different conf "oozie.server.authentication.type" to specify server-server authentication type.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)