Details

    • Improvement
    • Resolution: Unresolved
    • Major
    • None
    • None
    • Default
    • None

    Description

      I have a few Normal Users in my deployment who's access is controlled by Roles. The Roles are configured to allow access by Entity Group. The Role Members have access to entire Entity Groups, but in their view of the interface, the "Groups" menu item under devices is missing. Since users have access to multiple groups, it would be nice to retain the ability to see the different device groups in the devices menu. As it stands they can only see the complete list of all devices that are members of these groups.

      Attachments

        Activity

          [OBS-4844] Device Group Visibility for "Normal User"

          We limit access to groups because the interaction between the group code and the permissions code would be quite messy since groups can comprise entities not covered by the permissions system and it would likely be very slow the try to figure out which groups to show across all entity types, and displaying the rules to build the groups and even just the names of groups seemed like an information leak.

          Because of these reasons we decided to just limit visibility of the group system to global read users.

          adama Adam Armstrong added a comment - We limit access to groups because the interaction between the group code and the permissions code would be quite messy since groups can comprise entities not covered by the permissions system and it would likely be very slow the try to figure out which groups to show across all entity types, and displaying the rules to build the groups and even just the names of groups seemed like an information leak. Because of these reasons we decided to just limit visibility of the group system to global read users.

          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 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk
            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -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 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -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
            rhebert Ryan Hébert
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: