[
https://issues.apache.org/jira/browse/KNOX-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17360377#comment-17360377
]
Rohan Nimmagadda commented on KNOX-2612:
----------------------------------------
[~lmccay] thanks for the suggestions we made it work by changing the below
hadoop secure auth configs, before it was configured as "simple" auth type.
was wondering same "simple" auth properties workes fine until hadoop 3.2 we
starting seeing issue from Hadoop 3.3 libs.may be if any having similar issue
with Hadoop 3.3 clients hopefully this gives the solution.
"hadoop.http.authentication.cookie.domain": "nowhere.com",
"hadoop.http.authentication.simple.anonymous.allowed": "false",
"hadoop.http.authentication.type":"kerberos",
"hadoop.http.filter.initializers":"org.apache.hadoop.security.AuthenticationFilterInitializer
> 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)
