-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
[fixes #4480] OIDC Code Flow Quickstart #337
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It requires:
- a readme with the instructions to run the quickstarts
- tests (both JVM and native)
@cescoffier Tks for the review. Both items were added. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it possible to give more details about Keycloak, and start KC in the test.
import io.restassured.RestAssured; | ||
|
||
@QuarkusTest | ||
public class CodeFlowTest { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should try to start KC from the test.
I've found an example using TestContainer:
Can this be used?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure. I'll give it a try.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cescoffier Using testcontainers. As anything with Docker, users might experience unexpected errors due to environment settings. But it is indeed, a nice way to run tests using a container and an alternative to fabric8 plug-in.
I've merged it manually, because of the big rename. |
No description provided.