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

Update documentation with new authenticate usage on the CLI (#2865)

Browse Source 
* docs: update deploy-and-login getting started guide with new authenticate usage

* docs: update api-clients/cli.mdx to remove login-name flag when using authenticate

* docs: update common-workflows/manage-users-groups.mdx to remove login-name flag when using authenticate

* docs: update common-workflows/workflow-ssh-proxycommand.mdx with new short form usage of authenticate command when using the primary auth method in the global scope

* docs: update oss/installing/no-gen-resources.mdx to remove login-name usage in authenticate command

* docs: update oss/installing/run-and-login.mdx with short form usage of boundary authenticate

* docs: fix tabs

* docs: fix numbering

* Apply batch of suggestions from code review

Co-authored-by: Robin Beck <stellarsquall@users.noreply.github.com>

* docs: fix code blocks

* fixes code blocks

---------

Co-authored-by: Dan Heath <76443935+Dan-Heath@users.noreply.github.com>
Co-authored-by: Robin Beck <stellarsquall@users.noreply.github.com>
Co-authored-by: stellarsquall <stellarsquall@protonmail.ch>
This commit is contained in:
Jeff MalnickRobin BeckDan Heathstellarsquall
 authored and GitHub committed 2023-02-07 10:40:31 -05:00
1 parent 1e9057d8a3
commit eea5e80fa2
6 files changed
+31 -30
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

website/content/docs/common-workflows/workflow-ssh-proxycommand.mdx
+4 -3
View File
@@ -33,10 +33,11 @@ the local Boundary proxy in a wrapped netcat session, passing in the target ID a
## Authenticate to Boundary
Before `ssh` can invoke `boundary connect` you need to authenticate. In this example, we're using `boundary dev` with the
default username (admin) and password (password):
default username (admin) and password (password), and because this auth method is the primary that resides in the global
scope, we can use the short form of the authenticate command with no extra flags:
```bash
$ boundary authenticate password -login-name=admin -auth-method-id=ampw_1234567890
$ boundary authenticate
```
## SSH to Target
@@ -117,7 +118,7 @@ Before `ssh` can invoke `boundary connect` you need to authenticate. In this exa
default username (admin) and password (password):
```bash
$ boundary authenticate password -login-name=admin -auth-method-id=ampw_1234567890
$ boundary authenticate
```
## Authorize the Session