centersl/n8n-docs
1
0
Fork 0
mirror of https://github.com/n8n-io/n8n-docs.git synced 2026-03-27 09:28:43 +07:00
Code Issues Packages Projects Releases Wiki Activity

Apply suggestions from code review

Browse Source
This commit is contained in:
Deborah
2024-03-04 08:32:30 +00:00
committed by GitHub
parent 630fffe294
commit 255e952e3c
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/external-secrets.md
View File

@@ -71,8 +71,8 @@ For example, you have two n8n instances, one for development and one for product
Infisical version upgrades can introduce problems connecting to n8n. If your Infisical connection stops working, check if there was a recent version change. If so, report the issue to help@n8n.io.
### External secrets should only be set on credentials owned by an instance owner or admin
### Only set external secrets on credentials owned by an instance owner or admin
Due to the additional permissions that instance owners and admins have, it would be possible to update credentials owned by another user with a secrets expression. Whilst this will preview correctly for an instance owner or admin, the secret will not resolve when the workflow is run in production.
Due to the additional permissions that instance owners and admins have, it is possible for owners and admins to update credentials owned by another user with a secrets expression. This will preview correctly for an instance owner or admin, but the secret will not resolve when the workflow is run in production.
Therefore, it's important that external secrets are only used on credentials that are owned by an instance admin or owner to ensure they are resolved when a production execution occurs.
Only use external secrets for credentials that are owned by an instance admin or owner. This ensures they resolve correctly in production.