8000 Use BeanParam instead of direct parameters · Issue #48650 · keycloak/keycloak · GitHub
[go: up one dir, main page]

Skip to content

Use BeanParam instead of direct parameters #48650

Description

@shawkins

Description

The list endpoint methods of the current admin api, and even what is proposed for admin api v2, will contain quite a few parameters. As we add parameters, direct usage of the interface methods is problematic and will require either adding a new default method, or changing the existing calls.

We should instead use BeanParam objects such that the parameters can have a builder with a stable api.

Activity

  1. added this to the 26.7.0 milestone on May 1, 2026
  2. added theissue type on May 1, 2026
  3. shawkins commented on May 4, 2026

    @shawkins
    ContributorAuthor

    When this is worked we can decide if projection is needed for a single client.

  4. added a commit that references this issue on May 20, 2026
    a2ee11d
  5. added a commit that references this issue on May 22, 2026
    26ef6d1
  6. 24 remaining items

  7. added a commit that references this issue on Jul 20, 2026
    4dd5b17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    Fields

    No fields configured for task.

    Projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    0