THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Proposal is to add a new ssl property (ssl-use-default-providersslcontext) to let Geode use default security provider context (provided by either JDK provided provider or a custom provider). When using SSL, current implementation allows developers to set several ssl-* properties to define paths, types and passwords to keystore and truststores. Geode loads key & trust stores and initializes TrustManagerFactory(TMF) and KeyManagerFactory(KMF) to be used for secure socket management. This imposes certain limitations for developers who wants to bring in their custom implementation for some of the SPIs (Keystore/Truststore SPI, KeyManagerFactory/TrustManagerFactory SPI). Using this proposed new property ssl-use-default-providersslcontext=true, developers can let Geode initialize the TrustMangaer & KeyManager that are default context provided by the security provider and not loading keystores/truststores by using specific filesystem path.
...
Eg: When using Geode on CloudFoundry, applications running using java-buildpack can take advantage of buildpack's "ContainerSecurityProvider", which provides a custom implementation for TurstMangaer and KeyManager and reads CERTs from environmental variables.
How Geode uses this flag:
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
... ... private TrustManager[]SSLContext getTrustManagerscreateAndConfigureSSLContext() throws KeyStoreExceptionGeneralSecurityException, NoSuchAlgorithmException, CertificateException, IOException { if (sslConfig.isUseDefaultProvideruseDefaultSSLContext()) { TrustManagerFactory tmf =return TrustManagerFactorySSLContext.getInstancegetDefault(TrustManagerFactory.getDefaultAlgorithm()); tmf.init((KeyStore) null);} SSLContext newSSLContext return= tmf.getTrustManagersgetSSLContextInstance(); } else { //current implementation of reading truststore and initializing TMF ... ... } } private KeyManager[] getKeyManagers()keyManagers throws KeyStoreException, IOException, NoSuchAlgorithmException, CertificateException, UnrecoverableKeyException { if (sslConfig.isUseDefaultProvider()) { = getKeyManagers(); KeyManagerFactoryTrustManager[] keyManagerFactorytrustManagers = KeyManagerFactory.getInstance(KeyManagerFactory.getDefaultAlgorithm()getTrustManagers(); keyManagerFactorynewSSLContext.init(nullkeyManagers, trustManagers, null); /* use the return keyManagerFactory.getKeyManagers(); } else { //current implementation of reading keystore and initializing KMF default secure random */); ... ... } return newSSLContext; } ... ... |
How developers can use this flag on the client:
1. Implement custom provider as per JDK guidlines.
...
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
Properties pros = new Properties();
props.setProperty(ConfigurationProperties.SSL_ENABLED_COMPONENTS, SecurableCommunicationChannels.SERVER);
props.setProperty(ConfigurationProperties.SSL_REQUIRE_AUTHENTICATION, String.valueOf("true"));
props.setProperty(ConfigurationProperties.SSL_USE_DEFAULT_PROVIDERSSLCONTEXT, String.valueOf("true")); |
...