Resolving model export limitations in Sisense [Linux]
Step-by-Step Guide:
Starting soon, Snowflake will require Key Pair authentication for connections, and there's an important distinction in how Sisense and Snowflake currently recommend generating these keys.
Discrepancy in Key Pair Recommendations
Sisense Recommendation (Legacy)
Sisense has traditionally supported v1 key pairs:
openssl genrsa 2048 | openssl pkcs8 -topk8 -v1 'V1_ALGORITHM' -inform PEM -out rsa_key_1.p8
Snowflake Recommendation (Preferred)
Snowflake recommends using v2 key pairs:
openssl genrsa 2048 | openssl pkcs8 -topk8 -v2 des3 -inform PEM -out rsa_key.p8
----------------------------------------------------------
Solution: Use v2 Keys with Sisense 2025.2+
Good news: Sisense version 2025.2 introduces support for v2 key pairs, aligning with Snowflake’s preferred authentication mechanism.
Step-by-Step Migration Guide
Upgrade to Sisense 2025.2 or Later
Ensure your environment is running version 2025.2 or newer.
Check out the Sisense 2025.2 Release Notes (link to be added) for detailed compatibility and feature info.
Generate v2 Key Pairs
Run this command using openssl:
openssl genrsa 2048 | openssl pkcs8 -topk8 -v2 des3 -inform PEM -out rsa_key.p8
This will create a secure v2-compatible private key file (rsa_key.p8).
Configure Your Snowflake Connection in Sisense
In Sisense, go to Admin > Data > Connections.
Edit or create your Snowflake connection.
Upload the rsa_key.p8 file when setting up Key Pair authentication.
Ensure that the public key has been registered in Snowflake under the corresponding user account.
Troubleshooting Tips
Issue with Key Pair Authentication:
Ensure your version of Sisense is 2025.2 or later. Reverting to v1 key pairs is a temporary solution if your current version is below 2025.2.
Error Messages during Setup:
Verify that the key pair was generated following the exact command syntax and options as per Snowflake's recommendation.
Additional Information
It's advised to periodically check the Sisense documentation for any updates or changes in key pair authentication support.
References/Related Content:
Disclaimer: This post outlines a potential custom workaround for a specific use case or provides instructions regarding a specific task. The solution may not work in all scenarios or Sisense versions, so we strongly recommend testing it in your environment before deployment. If you need further assistance with this, please let us know.
