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

Tests with Keycloak container should not be started at Keycloak DEV mode #1580

Open
michalvavrik opened this issue Dec 18, 2023 · 0 comments
Labels
priority/high Issue of high severity that does not block next product release.

Comments

@michalvavrik
Copy link
Member

We keep repeating this pattern

mostly because we don't have configured HTTPS for all origins, but no users will actually do that in production, we need to have communication between Quarkus OIDC and Keycloak via secured channel and only start Keycloak in a production mode.

@michalvavrik michalvavrik added the priority/high Issue of high severity that does not block next product release. label Dec 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/high Issue of high severity that does not block next product release.
Projects
None yet
Development

No branches or pull requests

1 participant