mirror of
https://github.com/gravitational/teleport.git
synced 2026-11-04 19:05:37 +08:00
Paul Gottschling
7ef1e0549a
* Edit Database Access guides for Cloud users This edits Database Access guides that show you how to access specific databases. These guides follow the same structure and use the same partials, so it made sense to address them in a single commit. See #10637 Edits made - Some Prerequisites sections were either absent or required "Teleport," which I've clarified with a scoped Tabs component to indicate the appropriate client tools for each deployment type. Since we instruct users on deploying the Auth/Proxy later in the guide, I restricted this to client tools. Also flesh out the Prerequisites a bit in general. - Add ScopedBlocks for minor details that vary between scopes. - Ensure that all commands that take place on the Database Service node are described correctly as taking place on that node. - Change the tctl-auth-sign.mdx partial. Since the start-auth-proxy.mdx partial now instructs self-hosted users to run tctl commands on the Auth Service host, we no longer need the Self-Hosted tab. As a result, I have turned the Cloud tab into a ScopedBlock. - Reorder self-hosted guide sections so users start the Auth/Proxy before running "tctl auth sign". Otherwise, this command will not work. - Minor style/grammar tweaks * Respond to PR feedback
8 lines
274 B
Plaintext
8 lines
274 B
Plaintext
The Database Service requires a valid auth token to connect to the cluster. Generate
|
|
one by running the following command against your Teleport Auth Service and save
|
|
it in `/tmp/token` on the node that will run the Database Service:
|
|
|
|
```code
|
|
$ tctl tokens add --type=db
|
|
```
|