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

User role API allows to make role with no UI elements

XMLWordPrintable

    • Icon: Problem report Problem report
    • Resolution: Duplicate
    • Icon: Trivial Trivial
    • 6.0 (plan)
    • 5.4.0beta1
    • API (A)
    • Sprint 74 (Mar 2021), Sprint 75 (Apr 2021), Sprint 76 (May 2021), Sprint 77 (Jun 2021), Sprint 78 (Jul 2021), Sprint 79 (Aug 2021), Sprint 80 (Sep 2021)
    • 0.5

      Problem 1

      Create a user role (type:3) with only the Administration section UI elements enabled. Perform an update of this role by changing the type to 1.

      Observe that the user role is updated and no UI elements are enabled:

      When such a role is used it causes problems with the Frontend:

      PHP Fatal error:  Uncaught TypeError: Return value of CMenuHelper::getFirstMenuItem() must be an instance of CMenuItem, null returned

      Problem 2

      Steps to reproduce:

      1. Create rule with half UI elements visible, half not. Check 'default UI access'.
      2. Make rule.update changing only 'default UI access' to 0.
      3. Observed: an error message: "At least one UI element must be checked."
      4. Expected: successful update. Access to all current UI elements must remain same.

      Steps to reproduce:

      1. Create rule with half UI elements visible, half not. Uncheck 'default UI access'.
      2. Make rule.update changing only 'default UI access' to 1.
      3. Observed: successful update. But role now has access to all UI elements.
      4. Expected: successful update. Access to all current UI elements must remain same.

        1. image-2021-03-10-09-45-58-360.png
          30 kB
          Vjaceslavs Bogdanovs
        2. image-2021-03-10-09-47-54-707.png
          8 kB
          Vjaceslavs Bogdanovs

            vmurzins Valdis Murzins
            vjaceslavs Vjaceslavs Bogdanovs
            Team B
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: