Repository navigation
Replies: 2 comments
|
Hello team. We are having same performance problem with high volume LDAP authentication. Do you have a suggestion to improve the performance? |
0 replies
|
without pool it's generate bind/unbind for every ldap request ... can you use pool for every read operation and only no pool on authentication ? |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
In Keycloak, LDAP authentication does not use connection pooling, with the substantiation being:
Could we revisit this? In deployments with high volume of LDAP authentications, establishing a LDAP connection every time could have a significant performance impact (especially in the case of TLS connections).
Technically, it should be possible to reset the connection state to anonymous before returning it to the pool (and erase password from memory). However, the logic of that pool might differ from that of the pool we're using for LDAP data synchronization, and with JNDI we can have only one default pool (correct me if I'm wrong). This could be solved e.g. with Apache LDAP API (which is also way more powerful and versatile than JNDI).
On a related note, have we ever considered migrating from JNDI to Apache LDAP API in the long term?
All reactions