Page History

...

1. there is a single set of configuration options for SSL keystore, truststore, protocols and cipher-suites

2. a new "locator" component be added to the mix of cluster, server, http web and gateway components for SSL configuration

3. SSL can be enabled for all components or for selected components

4. Each component can be assigned an alias for certificate lookup in the key store.  If an alias is not assigned to a component it will use the default certificate in the key store.

...

ssl-enabled-components=[all, cluster, server, gateway, locator, httpweb, jmx]

all = any component being used will have SSL enabled

...

locator = communication between locators

http = hypertext transport protocol web = web-based communication

jmx = java management extension communications

Using component names like this is extensible so we will have minimal configuration changes if we add a new component.

ssl-certificaterequire-aliasauthentication=[emptytrue,stringfalse] (default "true")  – all component except web will be goverend by this setting

ssl- use first cert in keystore)web-require-authentication=[true,false] (default "false") – the web service (REST) can disable/enable mutual SSL authentication, due to the nature of how users use the web.

ssl-default-aliasssl-certificate-password=[empty,string] (default - use first cert in keystore)

ssl-protocols=space comma separated list (default "any")

ssl-ciphers=space comma separated list (default "any")

...

ssl-truststore-password=string

Alias overrides:

These Alias overrides allow you to configure different certificates for each component.  They override ssl-certificatedefault-alias and ssl-certificate-password for the specified component.

ssl-<component name>-certificate-alias=string  e.g ssl-<component name>-certificate-password=stringserver-alias, ssl-jmx-alias

Example: secure communications throughout

...

If the key store has multiple certificates you may want to specify the alias of the one you wish to use for each process.  For instance,

ssl-certificatedefault-alias=Hirokissl-certificate-password=changeit

Example: non-secure cluster communications, secure client/server

...

ssl-enabled-components=server,locator  NOTE: cluster SSL not enabled

ssl-server-certificate-alias=server

ssl-keystore=secure/keystore.dat

...

ssl-enabled-components=locator         NOTE: cluster SSL not enabled

ssl-locator-certificate-alias=locator

ssl-keystore=secure/keystore.dat

...

1. Should each component have an option to enable/disable ssl-require-authentication? All components except web should generally NOT disable mutual authentication. This would promote non-authenticated servers/clients connecting to the system. This is a security hole that we need the user to be aware of if they want to disable mutual authentication.

2. Most web  Most HTTP services, for instance, don't require client authentication.
      Resolution: new settings setting added.... ssl-web-require-authentication