[ 
https://issues.apache.org/jira/browse/KNOX-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17356601#comment-17356601
 ] 

Rohan Nimmagadda edited comment on KNOX-2612 at 6/3/21, 7:02 PM:
-----------------------------------------------------------------

it was working fine with Hadoop 3.2 + knox webHDFS , we started seeing Knox 
webHDFS issue with Hadoop 3.3

the namenode API works fine with curl request 

{{curl -u : 
"}}{{[http://namenode:port/webhdfs/v1/tmp/?user.name=user&op=LISTSTATUS|http://drcn1010.target.com:9870/webhdfs/v1/tmp/?user.name=z003k8q&op=LISTSTATUS]}}{{"}}

We are expecting to work same with Knox endpoint as well but its throughing an 
error 

curl -v -s -ik -u user:'pass' curl 
"https://knoxhost:8443/gateway/default/webhdfs/v1/tmp/?user.name=user&op=LISTSTATUS

Knox webHDFS API is not working either with user.name , doAs or without any 
flags getting same expectation 

 
{code:java}
{"RemoteException":\{"exception":"SecurityException","javaClassName":"java.lang.SecurityException","message":"Failed
 to obtain user group information: java.io.IOException: Security enabled but 
user not authenticated by filter"}
}
{code}


was (Author: rohannimmagadda):
it was working fine with Hadoop 3.2 + knox webHDFS , we started seeing Knox 
webHDFS issue with Hadoop 3.3

the namenode API works fine with curl request 

{{curl -u : 
"}}{{[http://namenode:port/webhdfs/v1/tmp/?user.name=user&op=LISTSTATUS|http://drcn1010.target.com:9870/webhdfs/v1/tmp/?user.name=z003k8q&op=LISTSTATUS]}}{{"}}

We are expecting to work same with Knox endpoint as well but its throughing an 
error 

curl -v -s -ik -u user:'pass' curl 
"https://knoxhost:8443/gateway/default/webhdfs/v1/tmp/?user.name=user&op=LISTSTATUS";

{"RemoteException":\{"exception":"SecurityException","javaClassName":"java.lang.SecurityException","message":"Failed
 to obtain user group information: java.io.IOException: Security enabled but 
user not authenticated by filter"}}

> Knox + webHDFS is not working with Hadoop 3.3 
> ----------------------------------------------
>
>                 Key: KNOX-2612
>                 URL: https://issues.apache.org/jira/browse/KNOX-2612
>             Project: Apache Knox
>          Issue Type: Bug
>          Components: KnoxSSO, Server
>    Affects Versions: 1.4.0, 1.5.0
>            Reporter: Rohan Nimmagadda
>            Priority: Blocker
>
> Hadoop 3.3 Webhdfs is not working with Knox end point getting below exception 
> Tried hadoop side of things by changing hadoop.http.filter.initializers in 
> core-site to default AuthFilter and 
> org.apache.hadoop.security.AuthenticationFilterInitializer value
> result shows same having issues with webHDFS
> Knox Webhdfs API : 
> [https://knoxhost:8443/gateway/default/webhdfs/v1/tmp/?|https://drcn1003.target.com:8443/gateway/bigred/webhdfs/v1/tmp/?]
>  &op=LISTSTATUS
> {"RemoteException":\{"exception":"SecurityException","javaClassName":"java.lang.SecurityException","message":"Failed
>  to obtain user group information: java.io.IOException: Security enabled but 
> user not authenticated by filter"}}
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to