Skip to content

Commit 92b4bab

Browse files
docs: add a note about known OIDC issue in Druid 35 (#800)
* docs: add a note about known OIDC issue in Druid 35 * Update docs/modules/druid/pages/usage-guide/security.adoc Co-authored-by: Malte Sander <contact@maltesander.com> --------- Co-authored-by: Malte Sander <contact@maltesander.com>
1 parent 1bfbc6e commit 92b4bab

1 file changed

Lines changed: 3 additions & 0 deletions

File tree

docs/modules/druid/pages/usage-guide/security.adoc

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -102,6 +102,9 @@ The secret containing the OIDC client credentials should be structured like this
102102
include::example$druid-oidc-authentication.yaml[tag=secret]
103103
----
104104

105+
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.
106+
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.
107+
105108
=== Current Limitations and Upcoming Work
106109

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

0 commit comments

Comments
 (0)