I'm not sure if users would have so many clients (feedback from real use
cases from the community is welcome). It seems we don't have pagination
today so I'm wondering if that is a problem for people using the console?
It is worth mention that this page makes much more sense for deployments
where users consent access to their information. For regular enterprise use
cases, where users are basically accessing internal apps to do their jobs,
I don't think this page adds much value. For instance, in this case, do
users need to consent/ and revoke access?
On Wed, Oct 2, 2019 at 2:11 PM Stan Silvert <ssilvert(a)redhat.com> wrote:
Specifically, we need to discuss filtering and pagination as it
to the "Applications" page:
The current design allows filtering by name and application type.
However, Stian has pointed out that some customers will have thousands
of clients. So this design might be unworkable.
I don't want to go too far into the weeds right now because I want to
understand the problem better first.
What is the use case when customers have many, many clients?
How common is it to have many, many clients for a single user?
What do those clients look like?
What could we use to filter on? The information we currently have on
the client side looks something like what you see here:
keycloak-dev mailing list