You can initialize the assigned JSSE provider with specific provider of own and trusted credentials that will be used during the secure HTTP communication. The provider supporting the custom loading of credentials has to provide a KeyManagerFactory/TrustManagerFactory implementation for a specific algorithm and optionally for a provider name in compliance with JSSE's SPI.

Credentials algorithm and optionally provider name are specified as values of the following "Configuration":

• For own credentials (key pair and own certificate chain) – kmfalgorithm and kmfprovider. You can also leave these properties unspecified and set values to the system properties mbs.http.keyManagerFactoryAlgorithm and mbs.http.keyManagerFactoryProvider. If the algorithm is not specified then the HTTP Bundle will use the Key Manager Factory in the JVM for the default algorithm.

  The Key Manager Factory will be initialized with the keystore specified with the system properties javax.net.ssl.keyStore, and javax.net.ssl.keyStorePassword if the keystore is compliant with the "JKS" provider. If the keystore supports another format, specify the relevant provider through the mbs.http.keystoreType system property. They should be set in the same way as described for the JVM's default JSSE provider.

• For trusted credentials – tmfalgorithm and tmfprovider. You can also leave these properties unspecified and set values to the system properties mbs.http.trustManagerFactoryAlgorithm and mbs.http.trustManagerFactoryProvider. If the algorithm is not specified as well, then the HTTP Bundle will rely on the JVM's trust management settings.