Network Atlas Permissions

I found that a user needs to have node management rights to be able to use Network Atlas.

This presents us with a bit of a security issue as we have a couple of users that have no business in the node management area, but they create and maintain all of our customers' maps (several hundred).

Is there any way to get this corrected so that an Admin without node management can access Network Atlas?

Thanks.

Find more posts tagged with

Security

network_atlas

access_denied

node_management

map

Accepted answers

bshopp

Understood and noted, thanks for posting this, I have opened an item in our tracking system

All comments

borgan

It should work to give the account only node management rights, but then not give the user a node list on his home page. That way, the user will not have access to any "manage nodes" links from his web home page.

Also, since the user would no doubt have maps on his home page, make sure you set his node details view to "none" so he can't drill down to nodes that way. If you do decide to allow the user a node details view, then you would have to make sure that view has no link to node management. For instance, the Node Details resource that can be placed in a Node Details view has a link to "Edit Node" on it that would allow the user to manage the node. Se what I mean?

See if this works for you.

bshopp

Let us know if what borgan suggessted works for you. We put this in place since Network Atlas can now be downloaded from Orion and run from any desktop and we didn't want just any Orion user to be able to go in there and muck around on the maps.

ctschap

I do understand the aim of how it was designed. However, I think this type of scenario may have been overlooked.

The users in question need Admin and Customize View rights but not Node Management for what they are tasked with.

They build the customer user accounts for the NPM web interface and they create the maps and put them on the customers' home views.

I am not overly concerned about the "Manage Nodes" or "Edit Node" links on the node details pages. However, these users will still need to be navigating to the general administration page for their duties and I don't want them getting curious about what "Manage Nodes" is all about.

bshopp

Understood and noted, thanks for posting this, I have opened an item in our tracking system

borgan

If the user needs to perform Admin functions, but you still want to keep them away from Manage Nodes, you could create a custom menu bar with links to specific admin functions from the Orion Website Administration.

For example, you Add a menu item with a link to the URL for Account Manager. That way they never have to see the full admin page with the link to Manage Nodes.

Would that work for you?