Nagios Support Forum

Can we get an option or something to not auto login the users into XI when they click something. If they are not already logged in, I would rather them have to login again that being automatically logged in with the server credentials. With that happening, I can not use Fusion.

Thanks

Can you maybe elaborate a little bit as to the "why" on this one? I want to make sure I understand the end goal on this. Are you needing the users to log in as a different user than what the Fusion credentials are?

Well...let me try and be more descriptive

I have XI server called server1 and have it setup in Fusion with credentials of user1 and password1
I logout of XI
I login to Fusion as user2 and password2
I click a link in Fusion and it opens XI but I cam logged in as user1 and not myself. So if I acknowledge anything, I would not be acknowledging as myself.

That enough explanation?

Yes, thank you : )

Now here's my question as long as I've got you on the line for this. Fusion needs a single "master" account to fetch the data and cache it locally. Would it be acceptable to have one master account fetching data for all users (keeping in mind the list of hosts and services will reflect the master account's permissions), but then the auto-login from Fusion be based on the user account?

The only reason this hasn't been implemented already was because of the need for caching and also to be able to honor environments with multi-tenancy.

For my environment, yes, that would work.

Good to know. This particular feature is a larger revision, so it may be a bit longer before this one shows up in Fusion. Addon components are quicker, but a change like this modifies how Fusion currently works, so it might have to be in a Fusion 2012r2.x version.

Being a Multi-site licensed customer, our organization has raised concerns with this issue hindering functionality of the product as well.

Support request: http://support.nagios.com/forum/viewtop ... 73&p=61046
Feature request: 0000436

We too would like to see some priority put on fixing this.

I will add a +1 to our internal tracker for features. I can definitely see where this would be useful and fairly logical!