You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sqoop.apache.org by "Richard (JIRA)" <ji...@apache.org> on 2015/03/26 08:35:54 UTC

[jira] [Updated] (SQOOP-1772) Sqoop2: Logically discern between kerberos and simple auth handling

     [ https://issues.apache.org/jira/browse/SQOOP-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard updated SQOOP-1772:
---------------------------
    Fix Version/s:     (was: 1.99.6)
                   2.0.0

> Sqoop2: Logically discern between kerberos and simple auth handling
> -------------------------------------------------------------------
>
>                 Key: SQOOP-1772
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1772
>             Project: Sqoop
>          Issue Type: Bug
>          Components: sqoop2-client
>    Affects Versions: 1.99.4
>            Reporter: Abraham Elmahrek
>             Fix For: 2.0.0
>
>
> Currently, Sqoop2 uses AuthenticatedURL in all cases since it falls back to simple authentication if kerberos is disabled. Soon, this won't be the case. So we should have different logic for simple authentication and kerberos authentication on the client side.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)