Page History
...
| Setting | Sample Value | Explanation |
|---|---|---|
https_with_hostname_verification | true | Specifies if hostname verification should be performed for HTTPS connections. |
keystore_path | ../../resources/https-keystore.p12 | The keystore includes the private key and server certificate created for incoming HTTPS connections (Server Authentication) and optionally for outgoing connections that request mutual authentication (Client Authentication). If separate certificates should be used then consider to store the Client Authentication certificate in the client keystore, see below. |
| PKCS12 | The keystore types PKCS12 and JKS are supported. |
keystore_password | The keystore is protected by a password. | |
key_password | The private keys in the keystore are protected by a password. Note that for PKCS12 keystores the same password applies to all keys. | |
client_keystore_path | ../../resources/https-client-keystore.p12 | The client keystore includes the private key and certificate for outgoing connections that request mutual authentication (Client Authentication) from a separate certificate. If a certificate is created for both Server Authentication and Client Authentication purposes then the keystore has to be used, see above. |
| PKCS12 | The client keystore types PKCS12 and JKS are supported. |
client_keystore_password | The client keystore is protected by a password. | |
client_key_password | The private keys in the client keystore are protected by a password. Note that for PKCS12 keystores the same password applies to all keys. | |
truststore_path | ../../resources/https-truststore.p12 | The truststore includes the public key and/or certificates for outgoing HTTPS connections (Server Authentication). |
truststore_type | PKCS12 | The truststore types PKCS12 and JKS are supported. |
truststore_password | The truststore is protected by a password. |
...
Overview
Content Tools