Nagios Support Forum

We have a KB site that describes our environment to Customers with access. We would like to provide a link where the customer can see the status of the servers that support their product (and ONLY the servers that support their product.) I saw a recent post where someone set up a special account to auto login when accessing the Nagios server. They were able to then provide a direct link to the dashboard and not be prompted for a login. This solution will not work in our environment though. We need provide a link where Client 1 can click and see client 1 servers, and client 2 can click another link and see only client 2 servers. If they elect to play around with the URL and attempt to gain greater access, we need them to be still only restricted to their own login.

We have been experimenting with this style of link. This format works for two of our Admin users, but no other accounts. (regardless of how 'Admin-like' we make the other accounts.)

Documentation indicates the above method is deprecated - being replaced by the REST API (thoroughly documented in the help section - thank you for that!). Unfortunately, our KB site is modular and we would need to buy the module to interpret JSON results. Additionally, we like the dashboard display, and would like to avoid re-inventing the wheel. Does anyone have experience using the username / ticket method? or know of a way to use the API Key to link directly to desired account and dashboard?

There isn't a very good way to do that with dashboards at the moment. Plenty of standing feature requests for the functionality you're looking for though, so it's on the radar for sure.

Unfortunately, our KB site is modular and we would need to buy the module to interpret JSON results.

Is there a particular data specification the KB site could accept without additional modules?

Is there a particular data specification the KB site could accept without additional modules?

HTML, Possibly PHP, but that may require more effort than we are willing to put into it. For now they will just have to log in.

Unless someone has discovered a way to do this without having to develop another whole web page, then this string could probably be closed.

You could also set up an account for auto-login (Admin -> Automatic Login), but that's only going to work for one specific user and the dashboards deployed to them. It wouldn't solve the multi-tenancy part of the equation.