You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We would like to use a private key stored in AWS KMS for authenticating using they Snowflake key pair auth mechanism. The current JDBC driver, which requires the actual content of the private key to be present in a local file. This isn't compatible with KMS, which never exposes the private key, but rather gives you access to a signing API.
It seems to me a straightforward way to accomplish this is to allow the library to be configured with a class name for a custom signing implementation. I will follow up shortly with a PR implementing this proposal.
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
Allow using a private key stored in AWS KMS for key pair auth
SNOW-576663: Allow using a private key stored in AWS KMS for key pair auth
Apr 15, 2022
This enhancement request is in the backlog of items for the team to review and take into consideration when planning for future improvements. No timeline attached - but it's on the table for the future. Thank you for bearing with us!
We would like to use a private key stored in AWS KMS for authenticating using they Snowflake key pair auth mechanism. The current JDBC driver, which requires the actual content of the private key to be present in a local file. This isn't compatible with KMS, which never exposes the private key, but rather gives you access to a signing API.
It seems to me a straightforward way to accomplish this is to allow the library to be configured with a class name for a custom signing implementation. I will follow up shortly with a PR implementing this proposal.
The text was updated successfully, but these errors were encountered: