Skip to content
This repository has been archived by the owner on Aug 1, 2022. It is now read-only.

[Research] Support for compliant secure storage #460

Closed
vmutafov opened this issue Sep 2, 2021 · 2 comments
Closed

[Research] Support for compliant secure storage #460

vmutafov opened this issue Sep 2, 2021 · 2 comments

Comments

@vmutafov
Copy link
Contributor

vmutafov commented Sep 2, 2021

We should add the Vault in order to store internally used XSK user data in a secure way. We should consider whose responsibility would be to host the Vault, would it be the customer or we're going to host it in a container deployed with the XSK. The goal of this task would be to make the XSK authenticate itself against the Vault and provide a JS facade for the Vault HTTP APIs. The location of the Vault should be specified initially as environment variables.

@ThuF
Copy link
Contributor

ThuF commented Sep 3, 2021

This should be considered as an “optional” dependency. The XSK should be able to run also without it.

@ThuF ThuF modified the milestones: 0.9.0, 1.0.0 Sep 7, 2021
@dpanayotov dpanayotov mentioned this issue Feb 18, 2022
4 tasks
@dpanayotov dpanayotov modified the milestones: 1.0.0, 0.15.0 Feb 18, 2022
@dpanayotov dpanayotov changed the title [Security] Add support for using Hashicorp Vault as a secure storage [Research] Support for compliant secure storage Feb 18, 2022
@dpanayotov dpanayotov modified the milestones: 0.15.0, 0.16.0 Feb 28, 2022
@dpanayotov
Copy link
Contributor

not relevant atm

@dpanayotov dpanayotov added the wontfix This will not be worked on label Apr 1, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants