[
https://issues.apache.org/jira/browse/KYLIN-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16620091#comment-16620091
]
XiaoXiang Yu commented on KYLIN-3565:
-------------------------------------
When a RuntimeExecption was thrown, the status code of response is 500(server
error). But when authentication failed, the status code is 401(unauthorized).
So the front end will show different msg according to status code.
> User login error message is inaccurate
> --------------------------------------
>
> Key: KYLIN-3565
> URL: https://issues.apache.org/jira/browse/KYLIN-3565
> Project: Kylin
> Issue Type: Bug
> Components: REST Service, Web
> Affects Versions: v2.4.1
> Environment: CentOS 6.7, HBase 1.2.0+cdh5.14.2+456
> Reporter: Marc Wu
> Assignee: XiaoXiang Yu
> Priority: Minor
> Labels: usability
> Fix For: v2.6.0
>
> Attachments: 2018-09-17_16-56-12.png, 2018-09-17_16-56-38.png,
> 2018-09-17_16-59-31.png, image-2018-09-17-20-22-20-294.png,
> image-2018-09-17-20-25-54-896.png
>
>
> Hi Kylin team,
>
> We found one issue when log in Kylin. The error message will misunderstood
> user.
>
> I couldn't log in Kylin even I input correct username & password (enable
> LDAP).
> So I checked the log on server, it showed me that there exist HBase
> connection issues.
> Root cause is that the HBase server which Kylin used as metadata server is
> down, but the login message showed me that I should check my username or
> password. It's really confusing.
> Then I read some source codes about login module, and found out Kylin shares
> the same error message for different cases.
>
> We suggested two options:
> # redirect to global error page when HBase connection fail after login,
> shows error message(e.g. System Error, please contact system administrator).
> # enhance the error code for login logic, make the error message more
> specific.
>
> There are login error message and the log. And I log in successfully after
> recover HBase servers.
> !image-2018-09-17-20-25-54-896.png!!image-2018-09-17-20-22-20-294.png!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
