mirror of
https://github.com/gravitational/teleport.git
synced 2026-11-04 19:12:46 +08:00
* 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
22 lines
578 B
Plaintext
22 lines
578 B
Plaintext
Teleport uses mutual TLS authentication with self-hosted databases. These
|
|
databases must be configured with Teleport's certificate authority to be
|
|
able to verify client certificates. They also need a certificate/key pair that
|
|
Teleport can verify.
|
|
|
|
<ScopedBlock scope={["cloud"]}>
|
|
|
|
Your Teleport Cloud user
|
|
must be allowed to impersonate the system role `Db` in order to be able to
|
|
generate the database certificate.
|
|
|
|
Include the following `allow` rule in in your Teleport Cloud user's role:
|
|
|
|
```yaml
|
|
allow:
|
|
impersonate:
|
|
users: ["Db"]
|
|
roles: ["Db"]
|
|
```
|
|
|
|
</ScopedBlock>
|