[
https://issues.apache.org/jira/browse/OOZIE-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13171247#comment-13171247
]
[email protected] commented on OOZIE-624:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/3069/#review3954
-----------------------------------------------------------
/trunk/client/src/main/java/org/apache/oozie/client/AuthOozieClient.java
<https://reviews.apache.org/r/3069/#comment8934>
we are adding a mechanism to allow custom authentications, still the logic
here is pretty much wired.
How about the following:
Having a protected method
Map<String,Class<? extends Authenticator>> getAuthenticators() { ... }
The Apache implementation would have the following entries:
null -> KerberosAuthenticator
simple -> PseudoAuthenticator
kerberos -> KerberosAuthenticator
then the logic is quite simple:
Authenticator authClass = getAuthenticators().get(authOptionValue);
if (authClass == null) {
throw INVALID AUTH MECHANISM
}
Authenticator auth = authClass.newInstance();
.newInstance();
if
- Alejandro
On 2011-12-10 01:24:41, Angelo K. Huang wrote:
bq.
bq. -----------------------------------------------------------
bq. This is an automatically generated e-mail. To reply, visit:
bq. https://reviews.apache.org/r/3069/
bq. -----------------------------------------------------------
bq.
bq. (Updated 2011-12-10 01:24:41)
bq.
bq.
bq. Review request for oozie.
bq.
bq.
bq. Summary
bq. -------
bq.
bq. This improvement is mainly to add client parameter options to handle user
specified authentication option. In Oozie-77, client authentication uses
fall-back strategy to handle authentication, such as kerberos -> simple. User
should allow to give parameter or property to specify which authentication to
use.
bq.
bq. A proposal is :
bq.
bq. -auth simple
bq. -auth kerberos
bq. -auth <auth_name>
bq.
bq.
bq. This addresses bug OOZIE-624.
bq. https://issues.apache.org/jira/browse/OOZIE-624
bq.
bq.
bq. Diffs
bq. -----
bq.
bq. /trunk/client/src/main/java/org/apache/oozie/cli/OozieCLI.java 1209346
bq. /trunk/docs/src/site/twiki/DG_CommandLineTool.twiki 1209346
bq. /trunk/core/src/main/conf/oozie-site.xml 1209346
bq. /trunk/client/src/main/java/org/apache/oozie/client/AuthOozieClient.java
1209346
bq.
bq. Diff: https://reviews.apache.org/r/3069/diff
bq.
bq.
bq. Testing
bq. -------
bq.
bq.
bq. Thanks,
bq.
bq. Angelo K.
bq.
bq.
> client side improvement of authentication for user defined options
> ------------------------------------------------------------------
>
> Key: OOZIE-624
> URL: https://issues.apache.org/jira/browse/OOZIE-624
> Project: Oozie
> Issue Type: Improvement
> Reporter: Angelo K. Huang
> Assignee: Angelo K. Huang
> Labels: authentication, hadoop, oozie
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> This improvement is mainly to add client parameter options to handle user
> specified authentication option. In Oozie-77, client authentication uses
> fall-back strategy to handle authentication, such as kerberos -> simple. User
> should allow to give parameter or property to specify which authentication to
> use.
> A proposal is :
> -auth simple
> -auth kerberos
> -auth <auth_name>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
