Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Quarkus Keycloak Admin Client Roles: inconsistent data type in the attribute scopeParamRequired of RoleRepresentation #45427

Open
RayanArgolo03 opened this issue Jan 7, 2025 · 2 comments
Labels
area/keycloak kind/bug Something isn't working triage/needs-feedback We are waiting for feedback.

Comments

@RayanArgolo03
Copy link

Describe the bug

Attribute scopeParamRequired data type is different of constructor param, whereas for instance RoleRepresentation i needs create an object and use set method, making the code more verbouse:

I can´t instance RoleRepresentation because param is primitive boolean while attribute is wrapper boolean

**public class RoleRepresentation {

protected Boolean scopeParamRequired;

public RoleRepresentation() {
}

public RoleRepresentation(String name, String description, boolean scopeParamRequired) {
    this.name = name;
    this.description = description;
    this.scopeParamRequired = scopeParamRequired;
}

public void setName(String name) {
this.name = name;
}**

Expected behavior

No response

Actual behavior

No response

How to Reproduce?

No response

Output of uname -a or ver

No response

Output of java -version

No response

Quarkus version or git rev

No response

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

@RayanArgolo03 RayanArgolo03 added the kind/bug Something isn't working label Jan 7, 2025
Copy link

quarkus-bot bot commented Jan 7, 2025

/cc @pedroigor (keycloak), @sberyozkin (keycloak)

@michalvavrik
Copy link
Member

michalvavrik commented Jan 9, 2025

hey @RayanArgolo03 , thank you for reporting this, but a lot of details is left for guessing, for example:

  • there is no reproducer
  • you don't mention quarkus version you are using
  • you don't mention Keycloak version you are using
  • Quarkus Keycloak Admin Client doesn't tell me if it is quarkus rest or the resteasy client (hopefully not much relevant)

my best guess is that what you are saying is that Keycloak resource has changed while Quarkus is using older Keycloak client API in the Quarkus version you are using. Please provide more info. I am afraid there won't be much we can do, but it is still important to understand the situation, thank you.

@michalvavrik michalvavrik added the triage/needs-feedback We are waiting for feedback. label Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/keycloak kind/bug Something isn't working triage/needs-feedback We are waiting for feedback.
Projects
None yet
Development

No branches or pull requests

2 participants