You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Sandor Molnar (Jira)" <ji...@apache.org> on 2022/07/19 14:43:00 UTC
[jira] [Work started] (KNOX-2782) Knox CLI user-auth-test command failure
[ https://issues.apache.org/jira/browse/KNOX-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on KNOX-2782 started by Sandor Molnar.
-------------------------------------------
> Knox CLI user-auth-test command failure
> ---------------------------------------
>
> Key: KNOX-2782
> URL: https://issues.apache.org/jira/browse/KNOX-2782
> Project: Apache Knox
> Issue Type: Bug
> Components: KnoxCLI
> Affects Versions: 1.6.0
> Reporter: Sandor Molnar
> Assignee: Sandor Molnar
> Priority: Major
> Fix For: 2.0.0
>
>
> There is an issue with KnoxCLI's {{user-auth-test}} command:
> {noformat}
> /opt/cloudera/parcels/CDH/lib/knox/bin/knoxcli.sh user-auth-test --cluster cdp-proxy-api --u SA_HDP_ADMIN_D --p <password>
> java.lang.IllegalArgumentException: Configuration error. Specified object [invalidRequest] with property [blockSemicolon] without first defining that object's class. Please first specify the class property first, e.g. myObject = fully_qualified_class_name and then define additional properties.
> org.apache.knox.gateway.util.KnoxCLI$LDAPCommand$BadSubjectException: Subject could not be created with Shiro Config at sections=main,urls
> For more information use --d for debug output.
> ERR: Unable to authenticate user: SA_HDP_ADMIN_D {noformat}
> The reason is, that 3 properties are added OOTB to the generated Shiro configuration, under the "{{{}main{}}}" section, as per KNOX-2455
> {noformat}
> params.putIfAbsent("main.invalidRequest.blockSemicolon", "false");
> params.putIfAbsent("main.invalidRequest.blockBackslash", "false");
> params.putIfAbsent("main.invalidRequest.blockNonAscii", "false"); {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)