mirror of
https://github.com/gravitational/teleport.git
synced 2026-11-04 19:12:46 +08:00
Paul Gottschling
e3b1c2906e
This change replaces all `Tile`s in the docs with lists of links. This achieves two things: - Helps us move toward a more text-focused look and feel for the docs. See gravitational/docs#93. - Makes it easier to reorganize the docs. Currently, there's no linting for internal links in `Tile` hrefs (See gravitational/docs#100). I used this script to edit each docs page, invoking the script for all MDX files in docs/pages: ``` gawk ' BEGIN{inopentag=0; indesc=0; desc=""; title=""; href="";} /<\/?TileSet>/{next;} /<Tile/ { inopentag=1; } inopentag==1 && /title=/{ title=gensub(/.*title="([^"]+)".*/, "\\1", "g", $0); } inopentag==1 && /href=/{ href=gensub(/.*href="([^"]+)".*/, "\\1", "g", $0); } inopentag==1 && />/ { inopentag=0; indesc=1; next; } indesc==1 && !/<\/Tile/{ gsub(/(\n|\t|\s{2,})/," ",$0); desc=desc ($0); next; } /<\/Tile/{ print "- [" title "](" href "):" desc; indesc=0; desc=""; title=""; href=""; next; } inopentag==0 && indesc==0{ print $0 } ' $1 > "$1.tmp"; cat "$1.tmp" > "$1"; rm "$1.tmp"; ``` I then cleaned up each file changed by the script and fixed any incorrect URLs.
31 lines
2.1 KiB
Plaintext
31 lines
2.1 KiB
Plaintext
---
|
|
title: Teleport Server Access Features and Introduction
|
|
description: Teleport Server Access features and introduction.
|
|
videoBanner: EsEvO5ndNDI
|
|
---
|
|
|
|
# Server Access
|
|
|
|
Teleport Server Access consolidates SSH access across all environments, decreases configuration complexity, supports industry best practices and compliance while giving complete visibility over all sessions and events.
|
|
|
|
Teleport Server Access is designed for the following kinds of scenarios:
|
|
|
|
1. When up to a vast number of clusters must be managed using the command-line (`tsh`) or programmatically (through the Teleport API) and you want to simplify your stack, security, and configuration complexity.
|
|
2. When security team members must track and audit every user session.
|
|
3. When Teleport users require a complete, dedicated, and secure SSH option (Teleport Node running in SSH mode) and more than a certificate authority (Teleport Auth) with proxy (Teleport Proxy).
|
|
4. When resource and network security must be maximized: SSH certificates over secret keys, Two-Factor Authentication (2FA), Single Sign-On (SSO), and short-lived certificates.
|
|
|
|
## Getting started
|
|
|
|
- [Get started](getting-started.mdx): Get started using Teleport Server Access in 10 minutes. Server access for most common SSH use-cases.
|
|
- [Integrate with OpenSSH](guides/openssh.mdx): SSO and short-lived certificates for OpenSSH.
|
|
|
|
## Guides
|
|
|
|
- [Using Teleport with PAM](./guides/ssh-pam.mdx): How to configure Teleport SSH with PAM (Pluggable Authentication Modules).
|
|
- [OpenSSH Guide](./guides/openssh.mdx): How to use Teleport on legacy systems with OpenSSH and sshd.
|
|
- [Recording Proxy Mode](./guides/recording-proxy-mode.mdx): How to use Teleport Recording Proxy Mode to capture activity on OpenSSH servers.
|
|
- [BPF Session Recording](./guides/bpf-session-recording.mdx): How to use BPF to record SSH session commands, modified files and network connections.
|
|
- [Restricted Session](./guides/restricted-session.mdx): How to configure and use Restricted Session to apply security policies to SSH sessions.
|
|
- [Visual Studio Code](./guides/vscode.mdx): How to remotely develop with Visual Studio Code and Teleport.
|