Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-1057

API Authentication broken in rev 7946

XMLWordPrintable

    • Icon: Incident report Incident report
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • 1.9.0 (alpha)
    • 1.9.0 (alpha)
    • API (A)
    • None

      Updated frontend to rev 7946 to verify bug fixes, however I'm now unable to login.

      This is how I sent authentication requests before the latest revision. (Sorry about the order, the JSON library I'm using sets the order)
      Sent: {"auth":"","id":0,"method":"user.authenticate","params":

      {"user":"apitest","password":"test"}

      ,"jsonrpc":"2.0"}
      Received: {"jsonrpc":"2.0","error":

      {"code":-32602,"message":"Invalid params.","data":"Not authorized"}

      ,"id":0}

      If I add an auth field to be the same as the user name, I get the following.
      Sent: {"auth":"apitest","id":0,"method":"user.authenticate","params":

      {"user":"apitest","password":"test"}

      ,"jsonrpc":"2.0"}
      Received: {"jsonrpc":"2.0","error":

      {"code":-32602,"message":"Invalid params.","data":"Not authorized"}

      ,"id":0}

      I have tried multiple user accounts all with proper permission for login via the API.

      As a side question, should the auth field be required to authenticate? I would think it should not, but it appears that it is now.

            Unassigned Unassigned
            redtux nelsonab
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: