-
As a user I want to be able securely store, provision and manage my secret data (passwords, encryption keys, certificates etc).
-
Hello,
I'm trying to getting an update of an existing User Account our Cyberark Vault to work. The Creation of the Account works fine. But when I try to update the Secret manually, I receive the fo…
-
This may or may not be more of a question than an issue, but anyway:
If we want our remotely executing builds to get access to secrets, what would be the best way for us to make those accessible to…
-
**What is missing?**
Like we modified the webhooks secret handling, we should also allow simplified management for internode encryption certificates. This might only require some documentation and tes…
-
## Summary
Currently there is not a robust way of exposing secrets for given users/groups in kuberentes jupyterlab.
## Proposed implementation
Using hashicorp vault within the QHub deploymen…
-
-
### Description
I am using docker for deployment which has the docker secrets for the management of secrets.
The secrets are stored in a file like for example `/run/secrets/password`.
I want to be …
-
### Version
Command Line Ubuntu Linux
### Suggestion
I'm not allowed to leave API keys in my files. I have to use a key manager such as: `secret-tool`. So instead of having to expose my API k…
-
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Community Note
* Please vote on this issue by adding a :thumbsup: [reaction](https://blog.github.com/2016-…
-
#### Proposal
To properly implement mTLS, we need to have a secret store/certificate system to:
- Store root mTLS signing certificates
- provide API access to distribute certificates to n…