Revert "Add documentation for moderated sessions (#9425) (#10302)"

This reverts commit e8ed183.
gravitational · Feb 16, 2022 · 03b8655 · 03b8655
1 parent 34bd99f
commit 03b8655
Show file tree

Hide file tree

Showing 41 changed files with 75 additions and 290 deletions.
diff --git a/docs/config.json b/docs/config.json
@@ -238,8 +238,7 @@
             { "title": "Second Factor - WebAuthn", "slug": "/access-controls/guides/webauthn/" },
             { "title": "Per-session MFA", "slug": "/access-controls/guides/per-session-mfa/" },
             { "title": "Dual Authorization", "slug": "/access-controls/guides/dual-authz/" },
-            { "title": "Impersonation", "slug": "/access-controls/guides/impersonation/" },
-            { "title": "Moderated Sessions", "slug": "/access-controls/guides/moderated-sessions/" }
+            { "title": "Impersonation", "slug": "/access-controls/guides/impersonation/" }
           ]
         },
         { "title": "Reference", "slug": "/access-controls/reference/" },

diff --git a/docs/pages/access-controls/getting-started.mdx b/docs/pages/access-controls/getting-started.mdx
@@ -122,7 +122,7 @@ Save this role as `interns.yaml`:
 
 ```yaml
 kind: role
-version: v5
+version: v4
 metadata:
   name: interns
 spec:

diff --git a/docs/pages/access-controls/guides.mdx b/docs/pages/access-controls/guides.mdx
@@ -23,7 +23,4 @@ layout: tocless-doc
   <li>
     [Locking](./guides/locking.mdx). Lock access to active user sessions or hosts.
   </li>
-  <li>
-    [Moderated Sessions](./guides/moderated-sessions.mdx). Require session auditors and allow fine-grained live session access.
-  </li>
 </ul>
diff --git a/docs/pages/access-controls/guides/dual-authz.mdx b/docs/pages/access-controls/guides/dual-authz.mdx
@@ -80,7 +80,7 @@ spec:
 version: v2
 ---
 kind: role
-version: v5
+version: v4
 metadata:
   name: access-plugin
 spec:
@@ -162,7 +162,7 @@ Create `dbadmin`, `reviewer` and `devops` roles:
 
 ```yaml
 kind: role
-version: v5
+version: v4
 metadata:
   name: reviewer
 spec:
@@ -171,7 +171,7 @@ spec:
       roles: ['dbadmin']
 ---
 kind: role
-version: v5
+version: v4
 metadata:
   name: devops
 spec:
@@ -183,7 +183,7 @@ spec:
           deny: 1
 ---
 kind: role
-version: v5
+version: v4
 metadata:
   name: dbadmin
 spec:

diff --git a/docs/pages/access-controls/guides/impersonation.mdx b/docs/pages/access-controls/guides/impersonation.mdx
@@ -32,7 +32,7 @@ Save this file as `jenkins.yaml` to create the user and role:
 
 ```yaml
 kind: role
-version: v5
+version: v4
 metadata:
   name: jenkins
 spec:
@@ -77,7 +77,7 @@ Save this role definition as `impersonator.yaml`:
 
 ```yaml
 kind: role
-version: v5
+version: v4
 metadata:
   name: impersonator
 spec:
@@ -179,7 +179,7 @@ allowed the impersonation of any users or roles with the label
 
 ```yaml
 kind: role
-version: v5
+version: v4
 metadata:
   name: security-impersonator
 spec:
@@ -214,7 +214,7 @@ Create a user and a role `security-scanner` using the following template:
 
 ```yaml
 kind: role
-version: v5
+version: v4
 metadata:
   name: security-scanner
   labels:
@@ -256,7 +256,7 @@ as the label on the role and/or user to impersonate:
 
 ```yaml
 kind: role
-version: v5
+version: v4
 metadata:
   name: security-impersonator
 spec:

diff --git a/docs/pages/access-controls/guides/locking.mdx b/docs/pages/access-controls/guides/locking.mdx
@@ -105,7 +105,7 @@ Create a role `locksmith`:
 
 ```yaml
 kind: role
-version: v5
+version: v4
 metadata:
   name: locksmith
 spec:
@@ -231,7 +231,7 @@ It is also possible to configure the locking mode for a particular role:
 
 ```yaml
 kind: role
-version: v5
+version: v4
 metadata:
     name: example-role-with-strict-locking
 spec:

diff --git a/docs/pages/access-controls/guides/moderated-sessions.mdx b/docs/pages/access-controls/guides/moderated-sessions.mdx
diff --git a/docs/pages/access-controls/guides/per-session-mfa.mdx b/docs/pages/access-controls/guides/per-session-mfa.mdx
@@ -87,7 +87,7 @@ Olga defines two Teleport roles: `access-dev` and `access-prod`:
 ```yaml
 # access-dev.yaml
 kind: role
-version: v5
+version: v4
 metadata:
   name: access-dev
 spec:
@@ -100,7 +100,7 @@ spec:
 ---
 # access-prod.yaml
 kind: role
-version: v5
+version: v4
 metadata:
   name: access-prod
 spec:

diff --git a/docs/pages/access-controls/guides/role-templates.mdx b/docs/pages/access-controls/guides/role-templates.mdx
@@ -36,7 +36,7 @@ We can create two roles, one for each user in file `roles.yaml`:
 
 ```yaml
 kind: role
-version: v5
+version: v4
 metadata:
   name: alice
 spec:
@@ -49,7 +49,7 @@ spec:
       '*': '*'
 ---
 kind: role
-version: v5
+version: v4
 metadata:
   name: bob
 spec:
@@ -78,7 +78,7 @@ Let's create a role template `devs.yaml`:
 
 ```yaml
 kind: role
-version: v5
+version: v4
 metadata:
   name: devs
 spec:
@@ -173,7 +173,7 @@ to be set by identity provider. Save this role as `sso-users.yaml`:
 
 ```yaml
 kind: role
-version: v5
+version: v4
 metadata:
   name: sso-users
 spec:
@@ -255,7 +255,7 @@ Let's see how these variables are used with role template `interpolation`:
 
 ```yaml
 kind: role
-version: v5
+version: v4
 metadata:
   name: interpolation
 spec:
@@ -288,7 +288,7 @@ behave as the following role:
 
 ```yaml
 kind: role
-version: v5
+version: v4
 metadata:
   name: interpolation
 spec:
-Original file line number
+Diff line change
@@ Expand Up / @@ -23,7 +23,4 @@ layout: tocless-doc @@
       <li>
         [Locking](./guides/locking.mdx). Lock access to active user sessions or hosts.
       </li>
-      <li>
-        [Moderated Sessions](./guides/moderated-sessions.mdx). Require session auditors and allow fine-grained live session access.
-      </li>
     </ul>