Open
Description
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.
- Pagination/Search for Tenants #2055
- Pagination/Search for Applications #2056
- Pagination/Search for Groups #2057
- Pagination/Search for Email Templates #2064
- Pagination/Search for Keys #2059
- Pagination/Search for API Keys #2060
- Pagination/Search for Identity Providers #2065
- Pagination/Search for User Comments #2061
- Pagination/Search for Themes #2058
- Pagination/Search for Webhooks #2066
- Pagination/Search for Lambdas #2067
- Pagination/Search for Consents #2068
- Pagination/Search for Forms #2193
- Pagination/Search for Forms Fields #2194
- Pagination/Search for Message Templates #2203
- Pagination/Search for Messages #2204
- Pagination for Report APIs #2231
- Possibility of retrieving all API Keys #1570 (needs arch discussion)
We may want to review caching tenants, but this should be avoided if possible.
Duplicates
Related
- [Enhance] Support Pagination on the Retrieve a User’s Comments API #71
- Patching an identity provider with a large number of applications takes too long #767
- Search API add option to retrieve actual hit count when result set exceeds the default 10k results #1086
- public-keys endpoint causing high db load #1145
- Alphabetize applications in drop down select boxes in UI #1668
- Search on custom data with the Search API (applications, tenants, etc) #1968
- More fields to add to existing Search APIs #2190
- Enhance Entity Grant Search/Retrieval APIs #2339
- Pagination/Search for Identity Providers Application Options #2657