Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SNOW-576663: Allow using a private key stored in AWS KMS for key pair auth #909

Open
meastham opened this issue Apr 15, 2022 · 0 comments · May be fixed by #910
Open

SNOW-576663: Allow using a private key stored in AWS KMS for key pair auth #909

meastham opened this issue Apr 15, 2022 · 0 comments · May be fixed by #910
Assignees
Labels
Backlog feature status-triage_done Initial triage done, will be further handled by the driver team

Comments

@meastham
Copy link

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.

@github-actions github-actions bot 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
@sfc-gh-dszmolka sfc-gh-dszmolka added the status-triage_done Initial triage done, will be further handled by the driver team label Apr 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backlog feature status-triage_done Initial triage done, will be further handled by the driver team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants