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

NetPath Permission Restrictions

Before I open a feature request, I wanted to make sure I'm not missing something. How can you restrict which users are allowed to create new netpaths and which ones cannot. Best I can tell it is based off of Node Management rights. However, not all of my users who manage nodes I want making netpaths.

Find more posts tagged with

NetPath

Accepted answers

All comments

neomatrix1217

I don't see that setting anywhere the only workaround I can think of is to remove netpath services from the Network_Tabmenu if that user has a customized menu bar.

ewoknophobia

Sweet work around, that will help buy me some time. I hope this is not the only way to control creations. I have a lot of users excited about reviewing the information, but don't have the infrastructure to support them making maps..

rmatejka

You are correct - currently creating new paths is tied to Node Management rights. If you had the option, how would you want to restrict access to the create path function?

ewoknophobia

To fit within the current user administration settings, I would add an additional setting configuration within the user/group set-up. Similar to NCM, it could allow rights to Read-Only, Create Paths, or No-Access. Or, it could be in the general settings for NPM, like Alert Management rights Yes vs. No, as NetPath Administration Yes vs. No.

bshuman

I would love to team up with a bunch of users and get some progress with a feature request. I manage a multi tenant Solarwinds Orion NOC and now all my customers are seeing our internal NetPath events. They don't have a NetPath menu nor Node management rights but NetPath events show up in every users event log.

I really need custom properties for NetPath probes so a user limitation can filter access and event logs for NetPath probes.

Kindest regards.

Manilyn_Ramos

but what if you only want the privilege access to the Netpath only and no access for the management node?

rob_a

I have the same issue too, on a multi-tenanted deployment. Also not worked out how to stop the Netpath from appearing in the events for those users, showing data for nodes that they otherwise cannot see due to account limitations. For customers, Netpath is removed from their menus, though they can still access by changing the URL. I have employed a workaround to stop access to the Netpath screens by changing the URL.

I have multiple additional web servers. The customer logins are directed to web servers where I have had to remove the netpath folder from IIS.

Simply rename c:\inetpub\SolarWinds\ui\modules\netpath to netpath.old.

Everytime the config wizard is run, that folder is restored, so I have a schedule task running every 15 minutes to check for the folder and rename/remove if present.

Similar issues with Appstack, as it does not comply 100% with account limitations against the custom property, so again customers could potentially see data on nodes they should not. For that renamed debug/default/settings.aspx in c:\InetPub\SolarWinds\Orion\AppStack to .aspx.old.

Again, I have a schedule task checking for those files, to mop up after the config wizard is run.

There does need to be more consistent permission management across the various modules. A feature request is required for Netpath permissions.

Best regards.

harry.griffiths

Hi Everybody,

Please do open a feature request, if you have not done so already!

Network Performance Monitor Feature Requests

Support can put feature requests through the backend to development through support tickets,

However it is recommended to also post to the specific request in the thwack community so others can vote.

Thanks in advance.

bshuman

Feature request has been created. Please Vote!

rob_a

As an update, I was advised by the support team that it was better to delete the netpath folder and appstack ASPX files rather than rename to .old.