umccr/htsget-rs

Crypt4GH secrets manager

Closed this issue · 3 comments

brainstorm commented

Instead of providing static paths resolving to secrets/keys for Crypt4gh, it should point to an endpoint that resolves to a key management service/server (HSM, HTTP endpoint, GitHub user.key, etc...)... like Elsa secrets provider (focusing on those that run on the server side, such as AWS Secrets Manager and just file-based for dev) /cc @andrewpatto .

brainstorm commented

@mmalenic I believe you implemented most of this in #271 ? ... not a custom API endpoint but perhaps it's good enough for now?

mmalenic commented

Yeah, it's probably okay for now. The Secrets Manager part is done, but it's not customizable beyond that.

brainstorm commented

We can reopen once more complexity is needed then!