diff --git a/docs/pages/access-controls/getting-started.mdx b/docs/pages/access-controls/getting-started.mdx index 1b3ecb7b07dfd..d88285308cfda 100644 --- a/docs/pages/access-controls/getting-started.mdx +++ b/docs/pages/access-controls/getting-started.mdx @@ -6,7 +6,7 @@ description: Get started using Teleport Access Controls. # Getting Started In Teleport, any local, SSO, or robot user can be a member of one or several -roles. Roles govern access to databases, SSH servers, kubernetes clusters, and web apps. +roles. Roles govern access to databases, SSH servers, Kubernetes clusters, Windows desktops and web apps. We will start with local users and preset roles, map SSO users to roles and wrap up with creating your own role. @@ -14,7 +14,7 @@ with creating your own role. ## Prerequisites - Installed [Teleport](../getting-started.mdx) or [Teleport Cloud](../cloud/introduction.mdx) >= (=teleport.version=) -- [Tctl admin tool](https://goteleport.com/teleport/download) >= (=teleport.version=) +- [tctl admin tool](https://goteleport.com/teleport/download) >= (=teleport.version=) (!docs/pages/includes/permission-warning.mdx!) diff --git a/docs/pages/enterprise/fedramp.mdx b/docs/pages/enterprise/fedramp.mdx index 60ab5963dd50d..d3057d584b04c 100644 --- a/docs/pages/enterprise/fedramp.mdx +++ b/docs/pages/enterprise/fedramp.mdx @@ -1,7 +1,7 @@ --- -title: FedRAMP compliance for SSH, Kubernetes and Applications -description: How to configure SSH, Kubernetes and Application access to be FedRAMP compliant, including support for FIPS 140-2 -h1: FedRAMP for SSH and Kubernetes and Application Access +title: FedRAMP compliance for Infrastructure access +description: How to configure SSH, Kubernetes, database, and web app access to be FedRAMP compliant, including support for FIPS 140-2 +h1: FedRAMP for SSH, Kubernetes, Databases and Web Apps. --- Teleport provides the foundation to meet FedRAMP requirements for the purposes of accessing infrastructure. This includes support for [FIPS 140-2](https://en.wikipedia.org/wiki/FIPS\_140-2), also known as the Federal Information Processing Standard, which is the US government approved standard for cryptographic modules. This document outlines a high diff --git a/docs/pages/enterprise/getting-started.mdx b/docs/pages/enterprise/getting-started.mdx index dd909cfbbdb39..95e0cdb135143 100644 --- a/docs/pages/enterprise/getting-started.mdx +++ b/docs/pages/enterprise/getting-started.mdx @@ -1,6 +1,6 @@ --- title: Teleport Enterprise Quick Start -description: How to set up and configure Teleport Enterprise for SSH and Kubernetes access +description: How to set up and configure Teleport Enterprise for SSH h1: Teleport Enterprise Quick Start --- diff --git a/docs/pages/enterprise/soc2.mdx b/docs/pages/enterprise/soc2.mdx index b56eb1780783c..55604d6879909 100644 --- a/docs/pages/enterprise/soc2.mdx +++ b/docs/pages/enterprise/soc2.mdx @@ -1,7 +1,7 @@ --- -title: SOC2 compliance for SSH, Kubernetes and Applications -description: How to configure SSH, Kubernetes and Application access to be SOC2 compliant -h1: SOC2 Compliance for SSH and Kubernetes and Application Access +title: SOC2 compliance for SSH, Kubernetes and Databases +description: How to configure SOC2-compliant access to SSH, Kubernetes, databases, desktops and web apps +h1: SOC2 Compliance for SSH, Kubernetes, Databases, Desktops and Web Apps --- Teleport is designed to meet SOC2 requirements for the purposes of accessing infrastructure, change management and system operations. This document outlines a high diff --git a/docs/pages/enterprise/sso.mdx b/docs/pages/enterprise/sso.mdx index 171d69ff725f2..1955751cbe639 100644 --- a/docs/pages/enterprise/sso.mdx +++ b/docs/pages/enterprise/sso.mdx @@ -1,6 +1,6 @@ --- title: SSO for SSH -description: How to set up single sign-on (SSO) for SSH using Gravitational Teleport +description: How to set up single sign-on (SSO) for SSH using Teleport h1: Single Sign-On (SSO) for SSH --- @@ -9,25 +9,25 @@ through a Single Sign-On (SSO) provider used the rest of the organization. - Configure Azure Active Directory SSO for SSH, Kubernetes, Database and Web apps. + Configure Azure Active Directory SSO for SSH, Kubernetes, databases, desktops and web apps. - Configure Windows Active Directory SSO for SSH, Kubernetes, Database and Web apps. + Configure Windows Active Directory SSO for SSH, Kubernetes, databases, desktops and web apps. - Configure Gsuite SSO for SSH, Kubernetes, Database and Web apps. + Configure Google Workspace SSO for SSH, Kubernetes, databases, desktops and web apps. - Configure Gitlab SSO for SSH, Kubernetes, Database and Web apps. + Configure GitLab SSO for SSH, Kubernetes, databases, desktops and web apps. - Configure OneLogin SSO for SSH, Kubernetes, Database and Web apps. + Configure OneLogin SSO for SSH, Kubernetes, databases, desktops and web apps. - Configure OIDC SSO for SSH, Kubernetes, Database and Web apps. + Configure OIDC SSO for SSH, Kubernetes, databases, desktops and web apps. - Configure Okta SSO for SSH, Kubernetes, Database and Web apps. + Configure Okta SSO for SSH, Kubernetes, databases, desktops and web apps. @@ -38,7 +38,7 @@ Users need to execute the following command login in the CLI or login using UI: ```bsh # this command will automatically open the default web browser and take a user # through the login process with an SSO provider: -$ tsh login --proxy=proxy.example.com +$ tsh login --proxy=proxy.example.com --auth=github # output: If browser window does not open automatically, open it by clicking on the link: diff --git a/docs/pages/enterprise/workflow/index.mdx b/docs/pages/enterprise/workflow/index.mdx index a36d3bf73c42b..16fa51de5b5de 100644 --- a/docs/pages/enterprise/workflow/index.mdx +++ b/docs/pages/enterprise/workflow/index.mdx @@ -1,6 +1,6 @@ --- -title: Access Requests for SSH and Kubernetes Access -description: How to customize SSH and Kubernetes access using Teleport. +title: Access Requests for Infrastructure Access +description: Teleport allows users to request new roles with elevated privileges from the CLI or UI. Requests can be escalated via ChatOps or anywhere else via our flexible Authorization Workflow API. h1: Teleport Access Requests --- @@ -196,7 +196,7 @@ spec: # the `request_prompt` field can be used to tell the user what should # be supplied in the request reason field. request_prompt: Please provide your ticket ID -version: v3 +version: v5 ```