fusionauth-issues
fusionauth-issues copied to clipboard
Pagination for everyone! And all things!
The UI / API should account for a large number of Applications and Tenants
Description
If you have many tenants, you'll also have many applications. There are several use cases we've seen exceeding 5k tenants.
Solution
The API and UI for Applications, Groups and Tenants should be paginated to account for this scenario and ensure the UI and API perform well.
We may also want to load these pages via AJAX.
- [x] https://github.com/FusionAuth/fusionauth-issues/issues/2055
- [x] https://github.com/FusionAuth/fusionauth-issues/issues/2056
- [x] https://github.com/FusionAuth/fusionauth-issues/issues/2057
- [x] https://github.com/FusionAuth/fusionauth-issues/issues/2064
- [x] https://github.com/FusionAuth/fusionauth-issues/issues/2059
- [x] https://github.com/FusionAuth/fusionauth-issues/issues/2060
- [x] https://github.com/FusionAuth/fusionauth-issues/issues/2065
- [x] https://github.com/FusionAuth/fusionauth-issues/issues/2061
- [x] https://github.com/FusionAuth/fusionauth-issues/issues/2058
- [x] https://github.com/FusionAuth/fusionauth-issues/issues/2066
- [x] https://github.com/FusionAuth/fusionauth-issues/issues/2067
- [x] https://github.com/FusionAuth/fusionauth-issues/issues/2068
- [ ] https://github.com/FusionAuth/fusionauth-issues/issues/2193
- [ ] https://github.com/FusionAuth/fusionauth-issues/issues/2194
- [ ] https://github.com/FusionAuth/fusionauth-issues/issues/2203
- [ ] https://github.com/FusionAuth/fusionauth-issues/issues/2204
- [ ] https://github.com/FusionAuth/fusionauth-issues/issues/2231
- [ ] https://github.com/FusionAuth/fusionauth-issues/issues/1570 (needs arch discussion)
We may want to review caching tenants, but this should be avoided if possible.
Duplicates
- https://github.com/FusionAuth/fusionauth-issues/issues/748
Related
- https://github.com/FusionAuth/fusionauth-issues/issues/71
- https://github.com/FusionAuth/fusionauth-issues/issues/767
- https://github.com/FusionAuth/fusionauth-issues/issues/1086
- https://github.com/FusionAuth/fusionauth-issues/issues/1145
- https://github.com/FusionAuth/fusionauth-issues/issues/1668
- https://github.com/FusionAuth/fusionauth-issues/issues/1968
- https://github.com/FusionAuth/fusionauth-issues/issues/2190
- https://github.com/FusionAuth/fusionauth-issues/issues/2339
- https://github.com/FusionAuth/fusionauth-issues/issues/2657
This also extends into things like the "Add User Registration" form. The application select list seems to be sorted by application creation date, which can get "interesting" when you need to use it with a large number of applications. :) Even just an alpha sort there would be 👍
Thanks for the comment @Codelica - you're correct, this is an area that also needs improvement. We recently alphabetized the groups in Add Group Membership and in the Group selector on the User Search page.
We'll be sure to audit the front end for any selector such as this and either lazily load it or at least provide some sorting that makes sense.
I know we have some clients with 5k+ tenants, so not sure how we'll handle that in the UI as it relates to select boxes.
Maybe a typeahead select box? Something like this: https://twitter.github.io/typeahead.js/examples/ ?
😂