[
https://issues.apache.org/jira/browse/CASSANDRA-16666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17422722#comment-17422722
]
Stefan Miklosovic commented on CASSANDRA-16666:
-----------------------------------------------
I applied few changes. here
https://github.com/instaclustr/cassandra/commit/38c2881b063fb58e1622967a94e9e9b8fcc0e60a
Kubernetes example did not compile for me and it was also placing conf files
produced by test to dir in conf which would polute the repository on the next
commit instead of putting them to "build" and interacting with them there.
Otherwise it is just more about some formatting and similar stuff.
I run a build here:
https://app.circleci.com/pipelines/github/instaclustr/cassandra/516/workflows/21747bff-fd40-4016-b900-3f5a8c906653
I created a formal PR here: https://github.com/apache/cassandra/pull/1243
Jenkins build is cooking here:
https://ci-cassandra.apache.org/job/Cassandra-devbranch/1153/
Let's just sleep on this, I will probably merge on Friday's morning around 9am
UTC+2 if I dont get any sudden shower thoughts :)
> Make SSLContext creation pluggable/extensible
> ---------------------------------------------
>
> Key: CASSANDRA-16666
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16666
> Project: Cassandra
> Issue Type: Improvement
> Components: Messaging/Internode
> Reporter: Maulin Vasavada
> Assignee: Maulin Vasavada
> Priority: Normal
> Fix For: 4.x
>
> Attachments: Screenshot from 2021-09-28 10-56-24.png
>
>
> Currently Cassandra creates the SSLContext via SSLFactory.java. SSLFactory is
> a final class with static methods and not overridable. The SSLFactory loads
> the keys and certs from the file based artifacts for the same. While this
> works for many, in the industry where security is stricter and contextual,
> this approach falls short. Many big organizations need flexibility to load
> the SSL artifacts from a custom resource (like custom Key Management
> Solution, HashiCorp Vault, Amazon KMS etc). While JSSE SecurityProvider
> architecture allows us flexibility to build our custom mechanisms to validate
> and process security artifacts, many times all we need is to build upon
> Java's existing extensibility that Trust/Key Manager interfaces provide to
> load keystores from various resources in the absence of any customized
> requirements on the Keys/Certificate formats.
> My proposal here is to make the SSLContext creation pluggable/extensible and
> have the current SSLFactory.java implement an extensible interface.
> I contributed a similar change that is live now in Apache Kafka (2.6.0) -
> https://issues.apache.org/jira/browse/KAFKA-8890
> I can spare some time writing the pluggable interface and run by the required
> reviewers.
>
> Created [CEP-9: Make SSLContext creation
> pluggable|https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-9%3A+Make+SSLContext+creation+pluggable]
>
>
> cc: [~dcapwell] [~djoshi]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
