nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Account Limitation on Interface doesn't limit your ability to see all nodes.

kbuska

I setup a account limitation where I only allowed visibility into a few interfaces. When I logged on to view the results, I could still see all my nodes, just not the interfaces within those nodes. It would be awesome if NPM knew that if I'm limiting access to Interface A on Node A, I should really only be able to see Node A.

Thoughts?

-Ken

Find more posts tagged with

limit_account

Accepted answers

All comments

superfly

I have found a similar thing on certain pages. Some will display the restricted nodes, other views display everything.

To get around the issue, for restricted users, I've created their own menu bar and views. Then in Manage Views, I also set the limitation on "View Limitation" to just what they are allowed to see. This way I can have multiple dashboards for different sites, just displaying what they are interested in.

Hope that may help.

byrona

I run into this problem as well. Just to make sure I understand you, do you actually create a different view for each restricted user where the View Limitation is set to only the stuff they are allowed to see?

kbuska

I created a custom property on the interface level and populated the Retail Providers name in that field. I then created an Account Limitation to filter on that interface custom property. It appears to work better if I create my own menu but I still can view nodes and node details that I don't want our end users (Retail Providers) to see.

-Ken

kbuska

I will try a view limitation. as well, thanks!

-Ken

mharvey

You'd need to actually create both Node and Interface limitations. You'll still be able to see node information, but you can at least limit the nodes. There's no way to limit with just interface properties. They aren't as relational as one would hope. The web UI assumes that you want to limit interfaces, but since there is no node limitation then all nodes are permitted to the user.

Regards,

Matthew Harvey

Loop1 Systems

http://www.loop1systems.com

kbuska

This works for most situations but we have some instances where a switch could have multiple Retail Providers on a switch. Example. Port 1 is Retail Provider 1 and Port 2 is Retail Provider 2. I can’t specify multiple strings in a node custom property. Any thoughts how I can work around that?

-Ken

mharvey

Do the retailers have any commonalities such as location, region, or anything like that? The other option would be each retailer as a custom property as a yes/no, then create limitations on those. Then create a limitation for the node, and the interfaces on those nodes, that way they see the switch in terms of CPU, but only the interface they are limited to.

byrona

The problem that I run into that I can't get passed is making it so that a customer can't see the node, I only want them to see the interfaces on devices such as shared switches or routers. At the same time there are nodes that I want them to see everything on. As best I can tell, this just isn't' possible to have both of these things at the same time for one customer.

mharvey

You're correct, it's not possible. The way the program seems to be setup, you have to have access to the node in order to have access to the interface. This should probably be something that changes in the way limitations work, the problem I foresee with that would be how to get past the relational nature of nodes and interfaces in the database.

Regards,

Matthew Harvey