We're looking to do the same thing.
I was considering a external facing web proxy that passes requests to port 443 on our npm server where isp customers use a unique login to access a limited view of information.
It seems like that could be a very tedious solution to manage as customer base multiplied by interface, map, node, event, etc grows exponentially.
Did you ever come up with a feasible solution?
Well, we are sort of rolling this out this month. The model is basically:
Each customer gets a user account restricted to the interfaces they are interfaced on, and the nodes they have those interfaces on. We created custom views for the Interfaces, Nodes, and summary views, custom toolbars for navigation, and even edited graphics and the CSS to brand the portal. Then we published the whole outfit behind SSL to ensure encryption.
There's no easier way to "manage" the nodes/interface, but we are looking to integrate the logins next year with a (hopeful) migration to Netsuite for our business support system - let multiple customer users log in to the netsuite portal and then have it do the passed login off to Orion. This way we keep 1 account per customer.
I'd be happy to show you how we did it, drop me a note with your email and we can set something up.
We are looking to do that
I just woun't give customer acces to my NPM in any way.
You can get the customer usege from the DB and use tools likeSQL Server Reporting Services or Crystal-Reports to generate graph out of the data.