While attempting to establish a Snowflake database connection in Splunk DB Connect v3.18 using an RSA key pair, the following error is encountered:
This error indicates that the security toolkit used to generate the encrypted private key relies on an encryption schema not supported by the Java runtime.
By default, OpenSSL 1.1.g uses the PBES2 encryption scheme (OID: 1.2.840.113549.1.5.13) to encrypt generated private keys.
However, not all Java versions support this encryption scheme, leading to authentication failures when connecting to Snowflake.
Step 1: Validate DB Connection Configuration
Step 2: Check Internal Logs for Errors
index=_internal *TraceID*
Look for the error similar to:
net.snowflake.client.jdbc.SnowflakeSQLLoggedException: Private key provided is invalid or not supported: PBES2 SecretKeyFactory not available
If this error is present, it confirms that the RSA private key encryption scheme is incompatible with the Java runtime.
Step 3: Analyze Encryption Compatibility
To resolve this issue, generate a new private key using a compatible encryption scheme, such as PBE-SHA1-3DES or PBE-SHA1-2DES, by following these steps:
Step 1: Generate a New RSA Private Key
openssl genrsa 2048 | openssl pkcs8 -topk8 -inform PEM -v1 PBE-SHA1-3DES -out rsa_key.p8
Or
openssl genrsa 2048 | openssl pkcs8 -topk8 -inform PEM -v1 PBE-SHA1-2DES -out rsa_key.p8
This ensures that the generated private key is compatible with the Snowflake JDBC driver.
Step 2: Generate the Corresponding Public Key
openssl rsa -in rsa_key.p8 -pubout -out rsa_key.pub
Step 3: Assign the Public Key to the Snowflake User
ALTER USER INFACMI_User SET rsa_public_key='key_value';
Replace 'key_value' with the actual contents of the newly generated public key (rsa_key.pub)
Step 4: Configure Snowflake DB Connection in Splunk DB Connect
| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
29-Sep-2026
|
Initial Release |