Hacker News new | past | comments | ask | show | jobs | submit login

They're desperate to get off keycloak at my org. Not sure the specifics, but our users complain about Auth issues often, and the keycloak web interface is painfully slow too.



I’ve read you need to partition usage to limit each keycloak instance to about 1500 total users to avoid performance issues. Does this hold true in your org?


I work for a competitor. I haven't heard that, but have heard of perf problems with > 1000 realms (tenants).

https://keycloak.discourse.group/t/maximum-limit-of-realms/8... has some details, though comments are 1-2 years old so may be out of date.


I work with an org that has 10's of thousands of users on keycloak, so there must be a way around the problem. I'm not administering the instance for this project, so I have no direct insight into how they deal with it.


Not saying this isn't true, but wtf? How could such a laughable number of users cause any kind of performance issue?


It looks like it's 'entities' and not just 'users'. From the docs [0]:

  Keycloak allows you to create any number of realms and any number of clients and users in them. But you need to be thoughtful as you scale up because as the number of entities grows, Keycloak slows down. When you log in as a superuser in the admin panel, even if you have only 1,500 realms, it will take a few minutes or even crash on timeout. Creating a new realm will take about 20 to 30 seconds. You need to change your logic and interaction with Keycloak.
[0]: https://www.redhat.com/architect/oauth-20-authentication-key...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: