From 85070b075c9873ab9f9b4734641a083fb0a2d4a2 Mon Sep 17 00:00:00 2001 From: Dan Heath <76443935+Dan-Heath@users.noreply.github.com> Date: Mon, 9 Sep 2024 17:06:31 -0400 Subject: [PATCH] Update website/content/docs/configuration/credential-management/configure-credential-injection.mdx Co-authored-by: Robin Beck --- .../credential-management/configure-credential-injection.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/docs/configuration/credential-management/configure-credential-injection.mdx b/website/content/docs/configuration/credential-management/configure-credential-injection.mdx index 75f613c70b6..6c76b3868a6 100644 --- a/website/content/docs/configuration/credential-management/configure-credential-injection.mdx +++ b/website/content/docs/configuration/credential-management/configure-credential-injection.mdx @@ -15,7 +15,7 @@ Credential injection provides end users with a passwordless experience when they ## Requirements - This feature requires either HCP Boundary or Boundary Enterprise -- You must have an existing target available. To use injected application credentials to connect to a target that runs SSH, you must use an SSH target type. +- You must have an existing target available. If you use the SSH target type, the target must be configured with an injected application credential. - You must have configured either a static credential store or a Vault credential store: