Repository-Metriken
- Stars
- (34.398 Sterne)
- PR-Merge-Metriken
- (PR-Metriken ausstehend)
Beschreibung
Before reporting an issue
- I have read and understood the above terms for submitting issues, and I understand that my issue may be closed without action if I do not follow them.
Area
core
Describe the bug
When querying clients through the REST API or using the admin java library, the filter in the q param is ignored and all clients are returned as a response.
Example: <keycloak_url>/auth/admin/realms//clients?q=name:test&search=true
In the latest version no clients are returned even though a client with this name exists. I tried specifying keycloak.client.searchableAttributes as a jvm attribute but still doesn't work.
Version
21.1.1
Expected behavior
When using the q query param, the clients should be filtered by this parameter.
Actual behavior
Either all clients are returned in version 21.x.x or none in 23.x.x.
How to Reproduce?
- Create a new client in a keycloak realm
- Query the clients specifically by the name of this client
Anything else?
The client that I'm trying to find using the q filter: { "id": "...", "clientId": "test", "name": "test", "surrogateAuthRequired": false, "enabled": true, "alwaysDisplayInConsole": false, "clientAuthenticatorType": "client-secret", "redirectUris": [ "/" ], "webOrigins": [ "/" ], "notBefore": 0, "bearerOnly": false, "consentRequired": false, "standardFlowEnabled": true, "implicitFlowEnabled": false, "directAccessGrantsEnabled": true, "serviceAccountsEnabled": false, "publicClient": false, "frontchannelLogout": true, "protocol": "openid-connect", "attributes": { "oauth2.device.authorization.grant.enabled": "false", "client.secret.creation.time": "1704208338", "backchannel.logout.session.required": "true", "backchannel.logout.revoke.offline.tokens": "false" }, "authenticationFlowBindingOverrides": {}, "fullScopeAllowed": true, "nodeReRegistrationTimeout": -1, "defaultClientScopes": [ "web-origins", "roles" ], "optionalClientScopes": [ "address", "phone", "offline_access", "profile", "microprofile-jwt", "email" ], "access": { "view": true, "configure": true, "manage": true } }