-
-
Notifications
You must be signed in to change notification settings - Fork 892
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
Bitwarden provider #1515
Comments
hey @sHaggYcaT! Do you have any examples you can reference to which uses this API for getting the sensitive information? AFAIK (and from the documentation link you've just sent), there was no public method to return sensitive information. There is even a notice on the documentation page forwarding you to use the CLI:
|
OK. Than, I think, it doesn't work this way |
https://bitwarden.com/help/vault-management-api has API endpoints to manage secret items. Note that they are exposed via This has quite a lot of limitations and security issues but I think it's worth looking into. |
https://pkg.go.dev/github.com/cozy/cozy-stack/web/bitwarden Package bitwarden exposes an API compatible with the Bitwarden Open-Soure apps. |
From what I can tell, that Go client package is being used precisely for the same purpose in the Cozy stack — as a vault backend for application secrets. Correct me if I'm wrong. It also seems to be actively maintained. @gusfcarvalho, now that this package is available, could Bitwarden be re-considered as a provider in external-secrets? |
Copy of Bitwarden provider #1309 and external-secrets/kubernetes-external-secrets#675
It's an opensource and self-hosted security manager. Previous issue were closed because of incompatibility:
Actually, bitwarden has HTTP API (a standard/swagger REST API):
The text was updated successfully, but these errors were encountered: