Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Flatly)
  • No Skin
Collapse
Brand Logo

NetXMS Forum

  1. Home
  2. Support
  3. User Permission Problems

User Permission Problems

Scheduled Pinned Locked Moved Support
3 Posts 2 Posters 33.6k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • Dani@M3TU
    Dani@M3TU
    Dani@M3T
    wrote on last edited by
    #1

    We want to give some supporters rights limited to there sites in NetXMS. So we assign rights only to the 'site'-container in 'Infrastructure Services'. There I see these problems:

    1. The System Right 'View event log' also includes Syslog. Please add this to the admin guide.
    2. You cannot block access to Event-Monitor, Syslog-Monitor and SNMP Trap Monitor (the System Rights are only for the corresponding Logs in Menu 'View')
    3. In Alarm-, Event-, SNMP Trap-Log and Syslog the limited supporter can see all events, syslog-entries... of all nodes, not only the ones from the containers he has permission for. NetXMS should filter the log entries and only show entries of sources he has permission for. In the fiield 'source' he only sees the node-id for such entries but he sees all other fields like 'Host Name' and 'Message'. We cannot allow this.
    4. Would it be possible and reasonable to remove all menu items a user don't have permisison for? To get everytime this error message is not very user friendly: ‘Open log „syslog“ has encountered a problem. Cannot open server log „syslog“: Access denied
    1 Reply Last reply
    0
    • V
      V
      Victor Kirhenshtein
      wrote on last edited by
      #2

      Hi!

      1. I think that separate those two will be better. I'll do this for next release.
      2. Yes, this is a bug. Also notifications sometimes not filtered properly.
      3. You can turn on object-level access control in logs by setting server configuration variable ExtendedLogQueryAccessControl to 1. You can try that, but depending on number of objects that could lead to complicated and ineffective SQL queries.
      4. Yes, it's planned.

      Best regards,
      Victor

      1 Reply Last reply
      0
      • Dani@M3TU
        Dani@M3TU
        Dani@M3T
        wrote on last edited by
        #3

        Thanks Victor!

        to 3.:
        Works! Please at least fill in the description in the ServerConfigurationVariable documentation the wiki.

        1 Reply Last reply
        0

        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

        With your input, this post could be even better 💗

        Register Login
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        Powered by NodeBB Contributors
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups