NagiosXI SSO Import/Manage Users issue

[vlions]

Hi,

We've successfully configured SSO, but our organization has over 700K users.

The "Import/Save Users" button doesn't appear in the "Import/Manage Users" step. How have others resolved this?

[danielheaton]

I'm having a similar issue - completely unable to scroll down the list of usernames in the 'import/manage users' window, so unless your name is between Aaron and Adam, I can't assign you an SSO user...

Hoping I'm just being really dumb, but not having any luck on Edge, Firefox or Chrome

[vlions]

FYI; I opened a support case and received the following response;

===
We have identified this issue and will address this bug, in the next release(s). Nagios uses an internal process to address bug fixes, for future releases.

Nagios does not offer updates on bug fix status, however, you can check future releases for bug fixes by checking the changelog, as this is the method used to post updates for these types of issues:

https://www.nagios.com/changelog/ and look for our internal issue number in the changelog.

Thanks,
Nagios Support
===

[danielheaton]

Thank you!

[jsprouse]

Any update on this? It's got me dead in the water.

Anyone figure out a work-around?

[bbahn]

@jsprouse,

Apologies for the inconvenience here. There is a fix that will be in the 2.1 release. Thank you for your patience.

[danielheaton]

All working in the new release!

[bbahn]

Glad to hear it! We'll be slowly rolling out more improvements to SSO and its usability over time.

[jsprouse]

Any update on this? It's got me dead in the water.

Anyone figure out a work-around?

Still not able to import users.

50k users in tenant. They list correctly now, after several minutes, but the import button does nothing.

[bbahn]

@jsprouse,

Are you seeing any specific errors on the page? We're aware of SSO issues affecting some users due to resource limitations. As a workaround, we plan to introduce API endpoints for adding/editing SSO users by year-end, which should provide a more reliable solution. We're also working to enhance the UI to minimize these issues, but for larger user bases, API-based management will likely be the most efficient approach. Let us know if there are any specific errors you are seeing so we can assist further!