You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oozie.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2011/09/08 06:43:09 UTC

[jira] [Created] (OOZIE-151) GH-129: KerberosHadoopAccessorService should fallback from Kerberos to Simple

GH-129: KerberosHadoopAccessorService should fallback from Kerberos to Simple
-----------------------------------------------------------------------------

                 Key: OOZIE-151
                 URL: https://issues.apache.org/jira/browse/OOZIE-151
             Project: Oozie
          Issue Type: Bug
            Reporter: Hadoop QA


Oozie server at start up time should ALWAYS try to get a token from the KDC, if that succeeds Oozie will work against clusters with Kerberos and Simple security (Hadoop client handles this automatically). If it fails, Oozie should configure the client to work as Simple.

And the kerberos.enabled config property could be removed.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Closed] (OOZIE-151) GH-129: KerberosHadoopAccessorService should fallback from Kerberos to Simple

Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OOZIE-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roman Shaposhnik closed OOZIE-151.
----------------------------------

    Resolution: Fixed

> GH-129: KerberosHadoopAccessorService should fallback from Kerberos to Simple
> -----------------------------------------------------------------------------
>
>                 Key: OOZIE-151
>                 URL: https://issues.apache.org/jira/browse/OOZIE-151
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Hadoop QA
>
> Oozie server at start up time should ALWAYS try to get a token from the KDC, if that succeeds Oozie will work against clusters with Kerberos and Simple security (Hadoop client handles this automatically). If it fails, Oozie should configure the client to work as Simple.
> And the kerberos.enabled config property could be removed.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (OOZIE-151) GH-129: KerberosHadoopAccessorService should fallback from Kerberos to Simple

Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OOZIE-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099837#comment-13099837 ] 

Hadoop QA commented on OOZIE-151:
---------------------------------

tucu00 remarked:
really not a good idea, if for some reason KDC is down you don't want to start Oozie unsecure.

> GH-129: KerberosHadoopAccessorService should fallback from Kerberos to Simple
> -----------------------------------------------------------------------------
>
>                 Key: OOZIE-151
>                 URL: https://issues.apache.org/jira/browse/OOZIE-151
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Hadoop QA
>
> Oozie server at start up time should ALWAYS try to get a token from the KDC, if that succeeds Oozie will work against clusters with Kerberos and Simple security (Hadoop client handles this automatically). If it fails, Oozie should configure the client to work as Simple.
> And the kerberos.enabled config property could be removed.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira