cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maulin Vasavada (Jira)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-16666) Make SSLContext creation pluggable/extensible
Date Thu, 08 Jul 2021 17:58:00 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-16666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17377540#comment-17377540
] 

Maulin Vasavada commented on CASSANDRA-16666:
---------------------------------------------

Hi [~sumanth.pasupuleti] and [~stefan.miklosovic] thanks for comments. Sorry I missed them
before since I was just checking DISCUSS thread on the CEP :( 

 

Sumanth, I totally get what you are saying. However I feel the same way as you do that this
is just SSLContext pluggability change and your suggestion should be a follow-up on the CEP-9
change. 

 

Stefan, your point is valid but I can only verify a custom implementation with our company's
internal requirements. However it may be worth to provide a sample integration with HashiCorp
Vault for example to fetch keys/certs and have a PoC. Not sure where that sample can be hosted
though.


Based on the latest discussion around improving CEP process, we may need to copy paste this
discussion to DISCUSS thread also. Can you please post/copy your comments and I'd copy mine
there?

> 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
>
>
> 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: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message