Eric Yang updated HADOOP-13707:
          Resolution: Fixed
       Fix Version/s: 3.0.0-alpha2
    Target Version/s: 2.8.0, 2.9.0, 3.0.0-alpha2
              Status: Resolved  (was: Patch Available)

This is a intermediate step required to provide ability to expand security 
options for securing web interface.  Look forward to HADOOP-13119.  I just 
committed this.  Thank you, Yuanbo.

> If kerberos is enabled while HTTP SPNEGO is not configured, some links cannot 
> be accessed
> -----------------------------------------------------------------------------------------
>                 Key: HADOOP-13707
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13707
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Yuanbo Liu
>            Assignee: Yuanbo Liu
>              Labels: security
>             Fix For: 2.8.0, 2.9.0, 3.0.0-alpha2
>         Attachments: HADOOP-13707.001.patch, HADOOP-13707.002.patch, 
> HADOOP-13707.003.patch, HADOOP-13707.004.patch
> In {{HttpServer2#hasAdministratorAccess}}, it uses 
> `hadoop.security.authorization` to detect whether HTTP is authenticated.
> It's not correct, because enabling Kerberos and HTTP SPNEGO are two steps. If 
> Kerberos is enabled while HTTP SPNEGO is not, some links cannot be accessed, 
> such as "/logs", and it will return error message as below:
> {quote}
> Problem accessing /logs/. Reason:
> User dr.who is unauthorized to access this page.
> {quote}
> We should make sure {{HttpServletRequest#getAuthType}} is not null before we 
> invoke {{HttpServer2#hasAdministratorAccess}}.
> {{getAuthType}} means to get the authorization scheme of this request

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org

Reply via email to