[
https://issues.apache.org/jira/browse/OOZIE-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14175419#comment-14175419
]
Robert Kanter commented on OOZIE-1688:
--------------------------------------
Can you put this line from the documentation back? I think it helps clarify
why there's a bunch of steps listed afterwards
{quote}Below are some additional steps and information specific to Oozie
HA:{quote}
It can be moved to after the oozie.server.authentication.type "</verbatim>"
section and before the " 1. (Optional) ..."
+1 after that; however, can you wait for OOZIE-1890 so you can replace
{{Services.get().getConf().get(...)}} with the new way of getting configs
{{ConfigurationService.OozieConfigs.get(...)}}
> 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-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)
