Find a X509 key manager compatible with a particular algorithm
Find a X509 key manager compatible with a particular algorithm
Build a key manager from a keystore.
Build a key manager from a keystore.
Pass None as arguments in order to get the default JVM key manager.
the keystore with which to initialize the keystore manager
a key manager
Constructs an SSL context with the given key settings.
Constructs an SSL context with the given key settings.
The context will be initialized with a key/trust manager built from the given key settings in addition to the default JVM key/trust manager.
key settings to initialize context with
a new SSL context
Pass None parameter to get the default JVM trust manager.
Pass None parameter to get the default JVM trust manager.
the truststore with which to initialize the trust manager
Adds the given key settings to the SSL context.
Adds the given key settings to the SSL context.
Applications that wish to set SSL properties like javax.net.ssl.* can - instead of polluting system properties - register the key settings using this method.
keystore/truststore info to add to the JVM
Manages multiple different keystores/truststores for one JVM instance.
Removes the reliance on system properties to get SSL to work.
Usage:
MultiKeyStoreManager.registerKeyStores(IKeystoreSettings)
instead of:sys.props("javax.net.ssl.keyStore") = keystorePath
etc This class is not thread-safe. Note: Modules registering key/truststores using this object will trust all other truststores, in particular also truststores registered by other modules. Therefore, registering keystores like this is not recommended in multi-module applications unless no other option exists, since module A may inadvertedly trust a truststore registered by module B, which is hardly ever desired. A "module" is in this context something that uses truststores/keystores.
http://stackoverflow.com/questions/1793979/registering-multiple-keystores-in-jvm for some early inspiration