-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
Add Reactive Keycloak-X Admin Client #9539
Comments
Or maybe have some kind of artifact that simply defines the interfaces? |
I also think that is the best way to go, mainly because the library should work for Wildfly too. The main issue here should be related to how we create We should be able to leverage the existing JAX-RS client resources, right? Or do you expect changes in their definitions in order to work with RESTEasy Reactive Client? |
@sberyozkin @geoand Sent #10714 as the first step to enable using different JAX-RS Client implementations. It does not touch yet the JAX-RS client resources and some are still using RESTEasy specific APIs. |
👍🏼 |
…tations Closes keycloak#9539 Co-authored-by: geoand <geoand@gmail.com>
…tations Closes #9539 Co-authored-by: geoand <geoand@gmail.com>
…tations Closes keycloak#9539 Co-authored-by: geoand <geoand@gmail.com>
Description
Keycloak Admin Client currently depends on the blocking RESTEasy Client which makes it impossible to use it with Quarkus RESTEasy Reactive server or client extensions.
Adding a Reactive Admin Client in Keycloak-X which will depend on Quarkus Rest Client Reactive extension will resolve the problem
Discussion
No response
Motivation
No response
Details
No response
The text was updated successfully, but these errors were encountered: