Security
Custom KeyStore and TrustStore
A KeyStore used to store private key and identity certificates, which enables the connector to verify its identity to the corresponding application server in an SSL connection. On the other hand, a TrustStore is utilized to store certificates issued by Certified Authorities (CA) that authenticate the certificate presented by the application servers in an SSL connection.
The OData V2 Connectors enable secure communication with the corresponding application server using both the default Java KeyStore and TrustStore, as well as a custom KeyStore and TrustStore.
To enable custom KeyStore and TrustStore set the following properties:
# Absolute path to the custom KeyStore on the worker machine.
sap.odata.keystore.location = path/to/your/custom/KeyStore
# The password for the custom KeyStore.
sap.odata.keystore.password = password
# The type of the custom KeyStore.
# e.g. jceks, jks, dks, pkcs11, pkcs12
sap.odata.keystore.type = jks
# Absolute path to the custom TrustStore on the worker machine.
sap.odata.truststore.location = path/to/your/custom/TrustStore
# The password for the custom TrustStore.
sap.odata.truststore.password = password
# The type of the custom TrustStore.
# e.g. jceks, jks, dks, pkcs11, pkcs12
sap.odata.truststore.type = jks
# The protocol that is applied for the encrypted communication between connector and server, like SSL or TLS.
# e.g. SSL, SSLv2, SSLv3, TLS, TLSv1, TLSv1.1, TLSv1.2, TLSv1.3
sap.odata.sslcontext.protocol = SSL
Following types are supported file types for KeyStore and TrustStore: jceks, jks, dks or pkcs12.
The configuration sslcontext.protocol
sets the encryption protocol which will be used for the secure communication.
Supported Protocols
SSL, SSLv2, SSLv3, TLS, TLSv1, TLSv1.1, TLSv1.2 and TLSv1.3
Supported KeyStore and TrustStore Types
jceks, jks, dks, pkcs11, pkcs12
- The custom TrustStore and KeyStore connector configurations overwrite the specific SSL connection configuration for the involved connector and not the global JVM configuration.
- In the absence of any custom TrustStore or KeyStore definition, the system default is used.
- A password is always required for utilizing a custom TrustStore or KeyStore.
- The configuration parameters for the encryption protocol as well the KeyStore and TrustStore types are case-sensitive.