Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[v9] Updating quick start enterprise #11408

Merged
merged 2 commits into from
Mar 25, 2022
Merged

[v9] Updating quick start enterprise #11408

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
088ed3f
update enterprise
stevenGravy Mar 24, 2022
1a70668
Merge branch 'branch/v9' into stevenGravy/docsv9/updatedateenterprise
stevenGravy Mar 25, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 5 additions & 14 deletions docs/pages/enterprise/getting-started.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -224,15 +224,6 @@ spec:
- root
```

<Admonition
type="note"
title="Note"
>
Ignore `{{internal.logins}}` "allowed login" for now. It exists for
compatibility purposes when upgrading existing open source Teleport
clusters.
</Admonition>

You probably want to replace "root" with something else. Let's assume there will
be a local UNIX account called "admin" on all hosts. In this case you can
dump the role definition YAML into a file and update "allow/logins"
Expand All @@ -259,7 +250,7 @@ $ sudo tctl create -f role.yaml
Now, lets create a new Teleport user "joe" with "access" role:

```bsh
$ sudo tctl users add --roles=access joe
$ sudo tctl users add --roles=access --logins=joe,ubuntu,ec2-user joe

Signup token has been created and is valid for 1 hours. Share this URL with the user:
https://auth.example.com:3080/web/newuser/22e3acb6a0c2cde22f13bdc879ff9d2a
Expand Down Expand Up @@ -307,7 +298,7 @@ in Teleport always must to go through an SSH proxy, sometimes called an "SSH bas
title="Warning"
>
For the purposes of this quickstart we are using the `--insecure` flag which allows
us to skip configuring the HTTP/TLS certificate for Teleport proxy. Your browser will
us to skip configuring the HTTPS/TLS certificate for Teleport proxy. Your browser will
throw a warning **Your connection is not private**. Click Advanced, and **Proceed to 0.0.0.0 (unsafe)**
to preview the Teleport UI.

Expand All @@ -323,9 +314,9 @@ With a certificate in place, Joe can now interact with the Teleport cluster:

```bsh
# SSH into any host behind the proxy:
$ tsh ssh node.example.com
$ tsh ssh joe@node.example.com

# See what hosts are available behind the proxy:
# See what hosts are available behind the proxy (Unix user 'joe' should already exist on the node):
$ tsh ls

# Log out (this will remove the user certificate from ~/.tsh)
Expand Down Expand Up @@ -443,7 +434,7 @@ This example command will create a Teleport user called `testuser` which has the
`access` role. Feel free to change these to suit your needs.

```code
$ docker exec teleport tctl users add testuser --roles=access
$ docker exec teleport tctl users add --roles=access --logins=root,ec2-user,ubuntu testuser
```

When you run this command, Teleport will output a URL which you must open to complete the user signup process:
Expand Down