Uploaded image for project: 'Kylin'
  1. Kylin
  2. KYLIN-3565

User login error message is inaccurate

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • v2.4.1
    • v2.5.1
    • REST Service, Web
    • CentOS 6.7, HBase 1.2.0+cdh5.14.2+456

    Description

      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:

      1. redirect to global error page when HBase connection fail after login, shows error message(e.g. System Error, please contact system administrator).
      2. 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.

      Attachments

        1. image-2018-09-17-20-25-54-896.png
          162 kB
          Marc Wu
        2. image-2018-09-17-20-22-20-294.png
          21 kB
          Marc Wu
        3. 2018-09-17_16-59-31.png
          91 kB
          Marc Wu
        4. 2018-09-17_16-56-38.png
          162 kB
          Marc Wu
        5. 2018-09-17_16-56-12.png
          159 kB
          Marc Wu

        Issue Links

          Activity

            People

              emiya0306 Roger
              mwu_ Marc Wu
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: