CyberCoveLLC/threshold
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: Revise requirements for SSH targets (#4866)

Browse Source 
* docs: Revise requirements for SSH targets

* docs: Minor edit
This commit is contained in:
Dan Heath authored and GitHub committed 2024-06-03 14:09:25 -04:00
1 parent 97d749fa26
commit 2541a3c398
1 file changed
+2 -2
Download Patch File Download Diff File Expand all files Collapse all files
website/content/docs/concepts/domain-model/targets.mdx
+2 -2
View File
@@ -114,8 +114,8 @@ SSH targets use injected application credentials to authenticate an SSH session
Injected credentials allow users to securely connect to remost hosts using SSH, while never being in the possession of a valid credential for that target host.
The injected credentials can be a username/password or username/private key credential from Vault [credential libraries][] or they can be static [credentials][] or an SSH certificate from Vault SSH credential libraries.
You cannot establish an SSH connection to a target using brokered credentials.
If you do not configure injected credentials to make the SSH connection, any attempts to connect to the SSH target result in an error.
SSH targets require you to configure injected credentials to create a session.
If you attempt to create a session against an SSH target without configuring injected credentials, it results in an error.
However, you can use brokered credentials with SSH targets for purposes other than establishing the initial SSH connection.
SSH targets have the following additional attributes: