The idea is:
Introduce an administrative setting in n8n that allows workspace owners/admins to require all credentials to come from External Secrets providers (e.g., AWS Secrets Manager, Azure Key Vault, GCP Secrets Manager, etc).
My use case:
We plan to deploy n8n Enterprise across our organization, and a key security requirement is that credentials within n8n are managed via External Secrets. This provides adherence to our security best practices and prevents users from bypassing centralized controls by creating or storing credentials directly inside n8n.
I think it would be beneficial to add this because:
Enforcing External Secrets ensures that users cannot bypass established security controls, while also enforcing all workflows to adhere to organizational security best practices.
Any resources to support this?
It would be an addition onto the existing n8n External Secrets feature - External secrets | n8n Docs
Are you willing to work on this?
Not at this point in time.
