keycloak/keycloak

Evaluation in "Permission" tab for "Clients" resource type put first char from client id

Open

#42,904 opened on Sep 24, 2025

View on GitHub
 (6 comments) (1 reaction) (0 assignees)Java (8,346 forks)batch import
area/admin/fine-grained-permissionsarea/corehelp wantedkind/bugpriority/normalstatus/auto-bumpteam/core-iamteam/core-shared

Repository metrics

Stars
 (34,398 stars)
PR merge metrics
 (Avg merge 6d 19h) (384 merged PRs in 30d)

Description

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

While we try to evaluate permission for "Client" resource type result is "The selected user does not have access to the selected resource(s)". When we go to Network we see the evaluate method put first symbol from client id in Payload -> resources

Version

26.3.3

Regression

  • The issue is a regression

Expected behavior

Evaluate method correct put field from client id

Actual behavior

Evaluate method get only first symbol from client id

How to Reproduce?

  1. Go to "Permissions" tab
  2. Select tab "Evaluation"
  3. set user
  4. set "Resource type" to "Clients"
  5. Select any client
  6. select any authorization scope
  7. press button "Evaluate"

Anything else?

No response

Contributor guide

Research direction
Inspect the evaluate permission endpoint in the admin console API, trace the method that extracts the client resource ID from the request, and identify why only the first character is being sent. Look for serialization or string manipulation issues in the backend code.
Tech stack
java
Domain
backendauthorization
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitJava
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60