# Request to API =\> slow ldapsearch due to wildcard

**URL:** <https://forum.keycloak.org/t/request-to-api-slow-ldapsearch-due-to-wildcard/29683>\
**Category:** Getting advice\
**Created:** [March 4, 2025, 4:48pm UTC](https://forum.keycloak.org/t/request-to-api-slow-ldapsearch-due-to-wildcard/29683 "2025-03-04T16:48:42Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![pascal-tower](https://avatars.discourse-cdn.com/v4/letter/p/c5a1d2/32.png) [@pascal-tower](https://forum.keycloak.org/u/pascal-tower)\
**Post date:** [March 4, 2025, 4:48pm UTC](https://forum.keycloak.org/t/request-to-api-slow-ldapsearch-due-to-wildcard/29683/1 "2025-03-04T16:48:42Z")

</div>

Hello  
I request a user from keycloak API  
it takes long time because keycloak searches the user in the LDAP provider with slow filter:  
(uid=)

is there a way to avoid this slow ldap search please?

BR  
Pascal

---

<div class="post-metadata">

**Author:** ![pascal-tower](https://avatars.discourse-cdn.com/v4/letter/p/c5a1d2/32.png) [@pascal-tower](https://forum.keycloak.org/u/pascal-tower)\
**Post date:** [March 4, 2025, 4:49pm UTC](https://forum.keycloak.org/t/request-to-api-slow-ldapsearch-due-to-wildcard/29683/2 "2025-03-04T16:49:18Z")

</div>

sorry: ldap filter is ( uid = \* \< searched user name \> \*)

---

<div class="post-metadata">

**Author:** ![skydrinker-tox](https://yyz2.discourse-cdn.com/free1/user_avatar/forum.keycloak.org/skydrinker-tox/32/9789_2.png) [@skydrinker-tox](https://forum.keycloak.org/u/skydrinker-tox)\
**Post date:** [March 5, 2025, 3:39am UTC](https://forum.keycloak.org/t/request-to-api-slow-ldapsearch-due-to-wildcard/29683/3 "2025-03-05T03:39:47Z")

</div>

Hello @pascal-tower, when using the keycloak API, there is a parameter to specify if you want to do an exact search or not.  
For the admin REST API, it is documented here : [Keycloak Admin REST API](https://www.keycloak.org/docs-api/latest/rest-api/index.html#_users)  
Regarding the Keycloak Java API, the exact search is also available, and implemented for the LDAP Storage Provider ( look for `searchForUserStream()` and provide `UserModel.EXACT` in the params Map)
