8000 `org.keycloak.admin.client.resource.ClientsResource.findByClientId(String)` should return single item · Issue #155 · keycloak/keycloak-client · GitHub
[go: up one dir, main page]

Skip to content

org.keycloak.admin.client.resource.ClientsResource.findByClientId(String) should return single item #155

Open

Description

@lrozenblyum

Description

Currently org.keycloak.admin.client.resource.ClientsResource.findByClientId(String) returns a List but client id is unique so it should return a single ClientRepresentation (nullable or Optional).

Now clients of the method are forced to get the first element of the collection.

Discussion

No response

Motivation

No response

Details

No response

Activity

  1. mposolda commented on Apr 15, 2025

    @mposolda
    Contributor

    Thanks for the report. I agree that this is valid use-case. It has low priority for now, but contribution is welcome to eventually improve this.

    Just a note that it will need to probably deprecated existing method on ClientsResource and introduce new method (maybe something like findClientByClientId) and deprecate existing method. This is needed for the backwards compatibility.

    Also this will need to be fixed first in the keycloak/keycloak repository. Anyone is welcome to create dedicated issue in the keycloak/keycloak and send the PR there with the fix. If this is done, fix would then be added to keycloak-client automatically upon next sync (see the README and contribution guides for more details).

  2. added
    status/fixed-in-keycloakRefers to the issue, which is fixed in keycloak/keycloak and will be synced to keycloak-client later
    status/fix-in-keycloak-requiredRefers to the issue, which need fix in keycloak/keycloak and will be synced to keycloak-client later
    and removed
    status/fixed-in-keycloakRefers to the issue, which is fixed in keycloak/keycloak and will be synced to keycloak-client later
    on Apr 15, 2025
  3. Lunatix01 commented on May 27, 2025

    @Lunatix01

    I created an issue in keycloak/keycloak repo, It would be nice if someone could take a look at it whenever they have time, obviously, and I will open a pull request for it after we agree on the structure.

  4. shawkins commented on Mar 13, 2026

    @shawkins
    Contributor

    @mposolda this can be closed as the issue / pr have been closed in the other repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0