JSSE: add Security property to disable Java client session cache #225
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…fjsse.clientSessionCache.disabled
cconlon
assigned cconlon, wolfSSL-Bot and JacobBarthelmeh and unassigned cconlon and wolfSSL-Bot
JacobBarthelmeh
approved these changes
Oct 10, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds support for a new Java Security property which can be used to disable the Java client-side session cache. If this property is set to "true", it prevents wolfJSSE from storing sessions into the Java client session cache:
java.security:
Programmatically:
README.md has been updated with a note about this new property. JUnit test has been added to test that resumption is not done when set.