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

[v24.1.x] CORE-6896 dt/audit: enable oauth after keycloak is up #23281

Merged

Conversation

vbotbuildovich
Copy link
Collaborator

Backport of PR #23260

OAuth has a background loop that polls the OIDC discovery service
(configured via the cluster config `oidc_discovery_url`) for updates.
This background loop starts as soon as OAuth is enabled via the
`sasl_mechanisms` and `http_authentication` cluster configs.
`oidc_discovery_url` has a default value pointing to a Redpanda-hosted
OIDC configuration. However, we should not rely on this Redpanda-hosted
default OIDC endpoint in our tests and CI because it might be
temporarily unavailable and cause the tests to be flaky.

To fix this test being flaky, we only enable OAuth once the local
keycloak server is up and available to serve the OIDC discovery
endpoint.

(cherry picked from commit c81b977)
@vbotbuildovich vbotbuildovich added this to the v24.1.x-next milestone Sep 11, 2024
@vbotbuildovich vbotbuildovich added the kind/backport PRs targeting a stable branch label Sep 11, 2024
@pgellert pgellert merged commit c456a68 into redpanda-data:v24.1.x Sep 12, 2024
17 checks passed
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/backport PRs targeting a stable branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants