-
Notifications
You must be signed in to change notification settings - Fork 2.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 KeycloakTestResourceLifecycleManager #13957
Comments
@sberyozkin I would love to give it a crack. I think we are close to wrapping up the wiremock issues or opaque token. This would make testing quarkus services that use oidc with keycloak a breeze :) |
It should be called |
Hi @cemnura, OK, great, let us complete the wiremock issue first (I'll follow up with the docs) and then we'll discuss this one, cheers |
@cemnura Hi Cem - assigning to you as agreed, lets have a |
@sberyozkin I'm on it 😄 |
I figured out that the current I migrated the All previous test seems to be working. Also, I did not change the maven profile configurations so that it wont be a problem during CI pipeline. To run the test
|
Description
In many OIDC related tests we have to add
QuarkusTestResourceLifecycleManager
implementations which setup Keycloak - realm, client, users.@stuartwdouglas has proposed that we provide the one which can be reused in tests, which is a nice idea.
Implementation ideas
Users who would like to test
quarkus-oidc
against Keycloak should be able to type something like this:where
TestKeycloakRealmResourceManager.class
would by default set upquarkus
realm,quarkus-app
client, usersalice
asadmin
andbob
asuser
, something like that, and possibly be configurableCC @stuartwdouglas @pedroigor
@cemnura let me know please if it can be of interest once the wiremock issues are complete :-)
The text was updated successfully, but these errors were encountered: