Skip to content

Conversation

@Erasure5959
Copy link
Contributor

@Erasure5959 Erasure5959 commented Sep 30, 2025

Closes #43020

This PR aims to disable Secure Client-Initiated Renegotiation by default in Keycloak. The current configuration represents a potential attack vector via DoS; closing this avenue by default is desirable and should have no adverse side effects.

This is applicable to TLS 1.2 only; TLS 1.3 completely removes support for renegotiation.

The parameter  -Djdk.tls.rejectClientInitiatedRenegotiation=true disables Secure Client-Initiated Renegotiation in Keycloak to resolve a potential DoS vulnerability. Note this is applicable only to TLS 1.2.

Signed-off-by: Erasure5959 <[email protected]>
The parameter -Djdk.tls.rejectClientInitiatedRenegotiation=true disables Secure Client-Initiated Renegotiation in Keycloak to resolve a potential DoS vulnerability. Note this is applicable only to TLS 1.2.

Signed-off-by: Erasure5959 <[email protected]>
Signed-off-by: Alexander Schwartz <[email protected]>
@ahus1 ahus1 self-assigned this Oct 1, 2025
Copy link
Contributor

@ahus1 ahus1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for contributing this change! I see one of our tests failed, and I had to remove a blank from one of the scripts.

@ahus1 ahus1 enabled auto-merge (squash) October 1, 2025 13:50
@Erasure5959
Copy link
Contributor Author

Thank you for being open to the change and allowing me to contribute - apologies for my oversight. Much appreciated!

@ahus1 ahus1 merged commit 3d9eb43 into keycloak:main Oct 1, 2025
82 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Secure Client-Initiated Renegotiation - disable by default

2 participants