Skip to content

docs: add a note about known OIDC issue in Druid 35 #800

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.

Sign up for GitHub

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

Merged
dervoeti merged 3 commits into from
Mar 10, 2026
Merged

docs: add a note about known OIDC issue in Druid 35 #800

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
eb546ab
docs: add a note about known OIDC issue in Druid 35
dervoeti Mar 9, 2026
8e3cccb
Merge branch 'main' into docs/druid-35-oidc
dervoeti Mar 9, 2026
81c2263
Update docs/modules/druid/pages/usage-guide/security.adoc
dervoeti Mar 10, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions docs/modules/druid/pages/usage-guide/security.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -102,6 +102,9 @@ The secret containing the OIDC client credentials should be structured like this
include::example$druid-oidc-authentication.yaml[tag=secret]
----

NOTE: OIDC authentication may fail since Druid versions `35.x.x` and `36.x.x` due to a change in how the authentication method is selected when connecting to an OIDC provider.
If your OIDC provider (e.g. Keycloak) advertises `private_key_jwt` as a supported client authentication method, Druid may attempt to use it, which causes authentication to fail.

=== Current Limitations and Upcoming Work

At the moment you can either use TLS, LDAP or OIDC authentication but not a combination of authentication methods.
Expand Down