You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Kevin Risden (Jira)" <ji...@apache.org> on 2020/01/06 15:07:00 UTC
[jira] [Resolved] (KNOX-2101) knoxshell doesn't handle invalid TLS
well
[ https://issues.apache.org/jira/browse/KNOX-2101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Risden resolved KNOX-2101.
--------------------------------
Resolution: Fixed
> knoxshell doesn't handle invalid TLS well
> -----------------------------------------
>
> Key: KNOX-2101
> URL: https://issues.apache.org/jira/browse/KNOX-2101
> Project: Apache Knox
> Issue Type: Bug
> Components: KnoxShell
> Reporter: Kevin Risden
> Assignee: Ljmiv
> Priority: Major
> Labels: beginner, noob
> Fix For: 1.4.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> knoxshell doesn't handle invalid TLS well. TLS trust failure should have a nice message instead of just "Failure to acquire token. Please verify your credentials and Knox URL and try again."
> {code:java}
> # ./bin/knoxshell.sh init https://knox_host/default/knox-token
> Enter username: guest
> Enter password:
> log4j:WARN No appenders could be found for logger (org.apache.http.client.protocol.RequestAddCookies).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
> Failure to acquire token. Please verify your credentials and Knox URL and try again.
> {code}
> Most likely we have a too aggressive catch block. The interesting part is that this message is logged but other messages aren't most likely due to KNOX-2100
--
This message was sent by Atlassian Jira
(v8.3.4#803005)