Add pkcs12 support on cache server#201
Merged
dmercuriali merged 5 commits intodiennea:masterfrom Mar 18, 2025
Merged
Conversation
dmercuriali
force-pushed
the
support-pkcs12
branch
from
974726d to
75ef2cc
Compare
diegosalvi
approved these changes
Mar 17, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 fixes #200 by adding support for certificates in PKCS12 format on the cache-server. No new configuration properties were added, the p12 file must be configured using the existing
server.ssl.certificatefileandserver.ssl.certificatefilepasswordprops.I also fixed the cache-client so it can now be configured to check that the server certificate is in the truststore. Previously we accepted any cert, to allow the default server config (self-signed cert) to work.
By default we keep accepting everything, but it's possible to validate the server cert by
setting
sslInsecure=falsewhen creating theGenericNettyBrokerLocator, orpassing
blazingcache.locator.client.sslinsecure=falsein thejavax.cache.spi.CachingProvider#getCacheManagerURII hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004