[ https://issues.apache.org/jira/browse/KNOX-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17356497#comment-17356497 ]
Philip Zampino commented on KNOX-2612: -------------------------------------- Is this issue specifically about the impersonation options, or are you saying that Knox won't proxy webhdfs without them either? Can you attach any relevant excerpts from the Knox logs? > 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)