Uploaded image for project: 'Observium'
  1. Observium
  2. OBS-3987

Can't assign Port-Permission to user

Details

    • Bug
    • Resolution: Fixed
    • Major
    • None
    • None
    • Security
    • None
    • Observium 22.1.11848 (rolling)

    Description

      In the user menu the drop-down menu for "Select device" inside "Port-Permissions" container stays empty. It is not possible to select a device, and due to this it is no longer possible to give read-access to single ports to a normal user. In other containers the dropdown menu is working fine (see attachments).

      Attachments

        Activity

          [OBS-3987] Can't assign Port-Permission to user
          landy Mike Stupalov added a comment -

          Tnx, fixed in r11857.

          landy Mike Stupalov added a comment - Tnx, fixed in r11857.
          opteamax Jens Ott added a comment -

          The device is being monitored correctly, Admin account can see all graphs as expected. It is only not possible to assigne read-only access for any port to a normal user. Making the whole device visible to the users works. So the snmp-walk output does not make any sense in this case, as it works perfectly.

          opteamax Jens Ott added a comment - The device is being monitored correctly, Admin account can see all graphs as expected. It is only not possible to assigne read-only access for any port to a normal user. Making the whole device visible to the users works. So the snmp-walk output does not make any sense in this case, as it works perfectly.
          bot Observium Bot added a comment -

          General questions and device support can be discussed in our Discord channel, click here to join.

          Please make and attach additional information about the device:

          • full snmp dump from device: 

            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk
            		 
            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

            If device not support SNMP version 2c, replace -v2c with -v1.

          • If you have problems with discovery or poller processes, please do and attach these debugs: 

            ./discovery.php -d -h <device>
            		 
            ./poller.php -d -h <device>

          • additionally attach device and/or vendor specific MIB files

          This comment is added automatically.

          bot Observium Bot added a comment - General questions and device support can be discussed in our Discord channel, click here to join . Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk If device not support SNMP version 2c, replace -v2c with -v1. If you have problems with discovery or poller processes, please do and attach these debugs: ./discovery.php -d -h <device> ./poller.php -d -h <device> additionally attach device and/or vendor specific MIB files This comment is added automatically.

          People

            landy Mike Stupalov
            opteamax Jens Ott
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: