Connection Properties

[emabee]

Check if there is something we should add from
https://help.sap.com/docs/SAP_HANA_CLIENT/f1b440ded6144a54ada97ff95dac7adf/109397c2206a4ab2a5386d494f4cf75e.html

[emabee]

Elaboration:

Legend:
✅: solved already; ❓: further elaboration necessary;❗️: should be done; 🚫: Rejected.

---

✅ sessionVariable:<key-name> <session-variable-value>

Is handled through explicit methods on Connection, set_application, set_application_user, etc.

❗️ bindAddress

Allows 'disguising' the client behind a different IP address than what the OS would say.

-> Didn't find yet a way in rustls to specify this.

🚫 currentSchema <schema>

Default: CURRENT_USER. Sets the current schema which is used for identifiers without schema.

-> Can and should be done via SQL: SET SCHEMA <schema_name>

✅ Cursor holdability

NONE, COMMIT, ROLLBACK, COMMIT_AND_ROLLBACK

Implemented in ConnectionConfiguration.

🚫 Transaction Isolation

TRANSACTION_READ_COMMITTED, TRANSACTION_REPEATABLE_READ, TRANSACTION_SERIALIZABLE

Sets the isolation level for the connection.

-> Rejected: can be done through SQL "SET TRANSACTION ISOLATION LEVEL {isolation}"

❓ hdbuserstore - do we need such a thing?

(also relevant: virtualHostName).

-> make it pluggable through some parameter of type Option<Arc<dyn HdbUserstore>>?

❓ maxLazyDroppedStatements <number> (50)

Controls the maximum number of queued statements to be dropped.
Setting this value to 0 disables the lazy drop feature and causes a request to be sent to the server
each time a statement is dropped by the application.

-> this is a buffering for drop statements; can be done if there is really need for it

❓network group -> not yet understood

🚫 packetSize

Sets the maximum size of a request packet sent from the client to the server in bytes.
The minimum is 130,000 bytes.

-> Declined.

❓ Support for SOCKS5 proxy

✅ reconnect

Intentionally not fully implemented, because it eventually creates silently errors (e.g. by discarding open transactions).

❗️ webSocketURL (SAP HANA Service only) <websocket-URL>

Specifies the WebSocket URL used to connect to a single-node SAP HANA server.
The connection property value cannot be empty.

Security Connection Properties

❓ authenticationMethods <comma-separated-string>

Provides a comma-separated list of authentication methods to be used by the client.
Possible values are: password, pbkdf2, ldap, saml, jwt, saplogon, kerberos, sessioncookie, and X509.

❗️ authenticationX509 <string> <value-of-sslKeyStore>

Provides a string containing the X509 certificate or the name of a file containing the
X509 certificate. The certificate must be PEM-encoded in PKCS8 format.
Defaults to the existing value of sslKeyStore, if specified.

-> looks meaningful, as an alternative to getting the value of PASSWORD as a String

See also https://developers-qa-blue.wcms-nonprod.c.eu-de-2.cloud.sap/tutorials/hana-clients-x509.html

🚫 cseKeyStorePassword <string>

Provides the password for the local key store.
This option is required when using client-side encryption.
This must be at least eight characters and have at least one upper case character,
one lower case character, and one number.

-> Not applicable.

❗️hostNameInCertificate <string>

Specifies the host name used to verify the server’s identity.

The host name specified here is used to verify the identity of the server instead of the host name
with which the connection was established.

For example, in a single-host system, if a connection is established from a client on the same host
as the server, a mismatch would arise between the host named in the certificate (actual host name)
and the host used to establish the connection (localhost).

Note
If you specify * as the host name, this property has no effect. Other wildcards are not permitted.

🚫 keyStore <file> | <store name> <VM default>

Specifies the location of the Java keystore.

-> Not applicable.

🚫 keyStorePassword <password> <VM default>

Specifies the password used to access the private key from the keystore file.

Note
This property is not used for SAP HANA studio connections.

-> Not applicable.

🚫 keyStoreType <JKS> | <PKCS12> <VM default>

Specifies the Java keystore file format.

-> Not applicable.

❗️ sniHostname <string>

Specifies the name of the host that is attempting to connect at the start of the TLS handshaking
process.

(✅) sslKeyStore <string>

Specifies an alternative to the keyStore connection property.
This property allows you to specify the contents of the keystore file as a string.
The certificates and private keys must be PEM-encoded, and the private keys must be in PKCS8 format.

-> Already implemented with TLS options in URL and ConnectParamsBuilder.

❗️ sslSNIRequest

Boolean
TRUE
Specifies whether SNI (Server Name Indication) requests are enabled for TLS connections: TRUE/FALSE.

(✅) sslTrustStore <string>

Specifies an alternative to the trustStore connection property.
This property allows you to specify the contents of the trust store file as a string.
The certificates must be PEM-encoded.

-> Already implemented with TLS options in URL and ConnectParamsBuilder.

(✅) trustStore <file> | <store name> <VM default>

Specifies the path to the trust store file that contains the server’s public certificate(s).

Typically, the trust store contains the root certificate or the certificate of the certification authority that signed the server’s certificate(s).

-> Already implemented with TLS options in URL and ConnectParamsBuilder.

🚫 trustStorePassword <password> <VM default>

Specifies the password used to access the trust store file.

-> Out of scope.

🚫 trustStoreType <JKS> <VM default>

Specifies the file format of the trust store file.

-> Out of scope.

🚫 validateCertificate

Boolean, default TRUE. If set to true, specifies that the server’s certificate is validated.

Already implemented with TLS options in URL and ConnectParamsBuilder.