russjones commented 1 year ago

Manual Testing Plan

Below are the items that should be manually tested with each release of Teleport. These tests should be run on both a fresh installation of the version to be released as well as an upgrade of the previous version of Teleport.

[x] Adding nodes to a cluster @codingllama
- [x] Adding Nodes via Valid Static Token
- [x] Adding Nodes via Valid Short-lived Tokens
- [x] Adding Nodes via Invalid Token Fails
- [x] Revoking Node Invitation
[x] Labels @nklaassen
- [x] Static Labels
- [x] Dynamic Labels
[x] Trusted Clusters @espadolini
- [x] Adding Trusted Cluster Valid Static Token
- [x] Adding Trusted Cluster Valid Short-lived Token
- [x] Adding Trusted Cluster Invalid Token
- [x] Removing Trusted Cluster
- [x] Changing role map of existing Trusted Cluster
[x] RBAC @fspmarshall

Make sure that invalid and valid attempts are reflected in audit log.
- [x] Successfully connect to node with correct role
- [x] Unsuccessfully connect to a node in a role restricting access by label
- [x] Unsuccessfully connect to a node in a role restricting access by invalid SSH login
- [x] Allow/deny role option: SSH agent forwarding
- [x] Allow/deny role option: Port forwarding
- [x] Allow/deny role option: SSH file copying
[x] Verify that custom PAM environment variables are available as expected. @rosstimothy
[x] Users @tobiaszheller

With every user combination, try to login and signup with invalid second factor, invalid password to see how the system reacts.

WebAuthn in the release tsh binary is implemented using libfido2 for linux/macOS. Ask for a statically built pre-release binary for realistic tests. (tsh fido2 diag should work in our binary.) Webauthn in Windows build is implemented using webauthn.dll. (tsh webauthn diag with security key selected in dialog should work.)

Touch ID requires a signed tsh, ask for a signed pre-release binary so you may run the tests.

Windows Webauthn requires Windows 10 19H1 and device capable of Windows Hello.
- [x] Adding Users Password Only
- [x] Adding Users OTP
- [x] Adding Users WebAuthn
- [x] macOS/Linux
- [x] Windows
- [x] Adding Users via platform authenticator
- [x] Touch ID
- [x] Windows Hello
- [x] Managing MFA devices
- [x] Add an OTP device with tsh mfa add
- [x] Add a WebAuthn device with tsh mfa add
  - [x] macOS/Linux
  - [x] Windows
- [x] Add platform authenticator device with tsh mfa add
  - [x] Touch ID
  - [x] Windows Hello
- [x] List MFA devices with tsh mfa ls
- [x] Remove an OTP device with tsh mfa rm
- [x] Remove a WebAuthn device with tsh mfa rm
- [x] Attempt removing the last MFA device on the user
  - [x] with second_factor: on in auth_service, should fail
  - [x] with second_factor: optional in auth_service, should succeed
- [x] Login Password Only
- [x] Login with MFA
- [x] Add an OTP, a WebAuthn and a Touch ID/Windows Hello device with tsh mfa add
- [x] Login via OTP
- [x] Login via WebAuthn
  - [x] macOS/Linux
  - [x] Windows
- [x] Login via platform authenticator
  - [x] Touch ID
  - [x] Windows Hello
- [x] Login via WebAuthn using an U2F device
U2F devices must be registered in a previous version of Teleport.

Using Teleport v9, set auth_service.authentication.second_factor = u2f, restart the server and then register an U2F device (tsh mfa add). Upgrade the installation to the current Teleport version (one major at a time) and try to log in using the U2F device as your second factor - it should work.
- [x] Login OIDC
- [x] Login SAML
- [x] Login GitHub
- [x] Deleting Users
[x] Backends @timothyb89
- [x] Teleport runs with etcd
- [x] Teleport runs with dynamodb
- [x] Teleport runs with SQLite
- [x] Teleport runs with Firestore
[x] Session Recording @strideynet
- [x] Session recording can be disabled
- [x] Sessions can be recorded at the node
- [x] Sessions in remote clusters are recorded in remote clusters
- [x] Sessions can be recorded at the proxy
- [x] Sessions on remote clusters are recorded in the local cluster
- [x] With an OpenSSH server without a Teleport CA signed host certificate:
  - [x] Host key checking enabled rejects connection
  - [x] Host key checking disabled allows connection
[x] Enhanced Session Recording @jakule
- [x] disk, command and network events are being logged.
- [x] Recorded events can be enforced by the enhanced_recording role option.
- [x] Enhanced session recording can be enabled on CentOS 7 with kernel 5.8+.
[x] Restricted Session @jakule
- [x] Network request are allowed when a policy allow them.
- [x] Network request are blocked when a policy deny them.
[x] Audit Log @Joerger
- [x] Failed login attempts are recorded
- [x] Interactive sessions have the correct Server ID
- [x] server_id is the ID of the node in "session_recording: node" mode
- [x] server_id is the ID of the node in "session_recording: proxy" mode
- [x] forwarded_by is the ID of the proxy in "session_recording: proxy" mode
Node/Proxy ID may be found at /var/lib/teleport/host_uuid in the corresponding machine.

Node IDs may also be queried via tctl nodes ls.
- [x] Exec commands are recorded
- [x] scp commands are recorded
- [x] Subsystem results are recorded
Subsystem testing may be achieved using both Recording Proxy mode and OpenSSH integration.

Assuming the proxy is proxy.example.com:3023 and node1 is a node running OpenSSH/sshd, you may use the following command to trigger a subsystem audit log:
```
sftp -o "ProxyCommand ssh -o 'ForwardAgent yes' -p 3023 %r@proxy.example.com -s proxy:%h:%p" root@node1
```
[x] Interact with a cluster using tsh @capnspacehook

These commands should ideally be tested for recording and non-recording modes as they are implemented in a different ways.
- [x] tsh ssh \<regular-node>
- [x] tsh ssh \<node-remote-cluster>
- [x] tsh ssh -A \<regular-node>
- [x] tsh ssh -A \<node-remote-cluster>
- [x] tsh ssh \<regular-node> ls
- [x] tsh ssh \<node-remote-cluster> ls
- [x] tsh join \<regular-node>
- [x] tsh join \<node-remote-cluster>
- [x] tsh play \<regular-node>
- [x] tsh play \<node-remote-cluster>
- [x] tsh scp \<regular-node>
- [x] tsh scp \<node-remote-cluster>
- [x] tsh ssh -L \<regular-node>
- [x] tsh ssh -L \<node-remote-cluster>
- [x] tsh ls
- [x] tsh clusters
[x] Interact with a cluster using ssh @capnspacehook Make sure to test both recording and regular proxy modes.
- [x] ssh \<regular-node>
- [x] ssh \<node-remote-cluster>
- [x] ssh -A \<regular-node>
- [x] ssh -A \<node-remote-cluster>
- [x] ssh \<regular-node> ls
- [x] ssh \<node-remote-cluster> ls
- [x] scp \<regular-node>
- [x] scp \<node-remote-cluster>
- [x] ssh -L \<regular-node>
- [x] ssh -L \<node-remote-cluster>
[x] Verify proxy jump functionality @atburke Log into leaf cluster via root, shut down the root proxy and verify proxy jump works.
- [x] tls routing disabled
- [x] tsh ssh -J \<leaf.proxy.example.com:3023>
- [x] ssh -J \<leaf.proxy.example.com:3023>
- [x] tls routing enabled
- [x] tsh ssh -J \<leaf.proxy.example.com:3080>
- [x] tsh proxy ssh -J \<leaf.proxy.example.com:3080>
[x] tsh CA loading @lxea

Create a trusted cluster pair with a node in the leaf cluster. Log into the root cluster.
- [x] load_all_cas on the root auth server is false (default) - tsh ssh leaf.node.example.com results in access denied.
- [x] load_all_cas on the root auth server is true - tsh ssh leaf.node.example.com succeeds.
[x] X11 Forwarding @Joerger
- Install xeyes and xclip:
- Linux: apt install x11-apps xclip
- Mac: Install and launch XQuartz which comes with xeyes. Then brew install xclip.
- Enable X11 forwarding for a Node running as root: ssh_service.x11.enabled = yes
- [x] Successfully X11 forward as both root and non-root user
- [x] tsh ssh -X user@node xeyes
- [x] tsh ssh -X root@node xeyes
- [x] Test untrusted vs trusted forwarding
- [x] tsh ssh -Y server01 "echo Hello World | xclip -sel c && xclip -sel c -o" should print "Hello World"
- [x] tsh ssh -X server01 "echo Hello World | xclip -sel c && xclip -sel c -o" should fail with "BadAccess" X error

User accounting @tigrato

[x] Verify that active interactive sessions are tracked in /var/run/utmp on Linux.
[x] Verify that interactive sessions are logged in /var/log/wtmp on Linux.

Combinations @capnspacehook

For some manual testing, many combinations need to be tested. For example, for interactive sessions the 12 combinations are below.

[x] Connect to a OpenSSH node in a local cluster using OpenSSH.
[x] Connect to a OpenSSH node in a local cluster using Teleport.
[x] #20831
[x] Connect to a Teleport node in a local cluster using OpenSSH.
[x] Connect to a Teleport node in a local cluster using Teleport.
[x] Connect to a Teleport node in a local cluster using the Web UI.
[x] Connect to a OpenSSH node in a remote cluster using OpenSSH.
[x] Connect to a OpenSSH node in a remote cluster using Teleport.
[x] Connect to a OpenSSH node in a remote cluster using the Web UI.
[x] Connect to a Teleport node in a remote cluster using OpenSSH.
[x] Connect to a Teleport node in a remote cluster using Teleport.
[x] Connect to a Teleport node in a remote cluster using the Web UI.

Teleport with EKS/GKE @AntonAM

[x] Deploy Teleport on a single EKS cluster
[x] Deploy Teleport on two EKS clusters and connect them via trusted cluster feature
[x] Deploy Teleport Proxy outside GKE cluster fronting connections to it (use this script to generate a kubeconfig)
[x] Deploy Teleport Proxy outside EKS cluster fronting connections to it (use this script to generate a kubeconfig)

Teleport with multiple Kubernetes clusters @AntonAM

Note: you can use GKE or EKS or minikube to run Kubernetes clusters. Minikube is the only caveat - it's not reachable publicly so don't run a proxy there.

[x] Deploy combo auth/proxy/kubernetes_service outside a Kubernetes cluster, using a kubeconfig
- [x] Login with tsh login, check that tsh kube ls has your cluster
- [x] Run kubectl get nodes, kubectl exec -it $SOME_POD -- sh
- [x] Verify that the audit log recorded the above request and session
[x] Deploy combo auth/proxy/kubernetes_service inside a Kubernetes cluster
- [x] Login with tsh login, check that tsh kube ls has your cluster
- [x] Run kubectl get nodes, kubectl exec -it $SOME_POD -- sh
- [x] Verify that the audit log recorded the above request and session
[x] Deploy combo auth/proxy_service outside the Kubernetes cluster and kubernetes_service inside of a Kubernetes cluster, connected over a reverse tunnel
- [x] Login with tsh login, check that tsh kube ls has your cluster
- [x] Run kubectl get nodes, kubectl exec -it $SOME_POD -- sh
- [x] Verify that the audit log recorded the above request and session
[x] Deploy a second kubernetes_service inside another Kubernetes cluster, connected over a reverse tunnel
- [x] Login with tsh login, check that tsh kube ls has both clusters
- [x] Switch to a second cluster using tsh kube login
- [x] Run kubectl get nodes, kubectl exec -it $SOME_POD -- sh on the new cluster
- [x] Verify that the audit log recorded the above request and session
[x] Deploy combo auth/proxy/kubernetes_service outside a Kubernetes cluster, using a kubeconfig with multiple clusters in it
- [x] Login with tsh login, check that tsh kube ls has all clusters
[x] Test Kubernetes screen in the web UI (tab is located on left side nav on dashboard):
- [x] Verify that all kubes registered are shown with correct name and labels
- [x] Verify that clicking on a rows connect button renders a dialogue on manual instructions with Step 2 login value matching the rows name column
- [x] Verify searching for name or labels in the search bar works
- [x] Verify you can sort by name colum
[x] Test Kubernetes exec via WebSockets - client

Kubernetes auto-discovery @tigrato

[x] Test Kubernetes auto-discovery:
- [x] Verify that Azure AKS clusters are discovered and enrolled for different Azure Auth configs:
- [x] Local Accounts only
- [x] Azure AD
- [x] Azure RBAC
- [x] Verify that AWS EKS clusters are discovered and enrolled
- [x] Verify that GCP GKE clusters are discovered and enrolled
[x] Verify dynamic registration.
- [x] Can register a new Kubernetes cluster using tctl create.
- [x] Can update registered Kubernetes cluster using tctl create -f.
- [x] Can delete registered Kubernetes cluster using tctl rm.

Kubernetes Secret Storage @tigrato

[x] Kubernetes Secret storage for Agent's Identity
- [x] Install Teleport agent with a short-lived token
  - [x] Validate if the Teleport is installed as a Kubernetes Statefulset
  - [x] Restart the agent after token TTL expires to see if it reuses the same identity.
- [x] Force cluster CA rotation

Kubernetes Pod RBAC @tigrato

[x] Check if Roles prior to v6 are allowed to access all pods.
[x] Verify the following scenarios for kubernetes_resources:
- [x] {"kind":"pod","name":"*","namespace":"*"} - must allow access to every pod.
- [x] {"kind":"pod","name":"<somename>","namespace":"*"} - must allow access to pod <somename> in every namespace.
- [x] {"kind":"pod","name":"*","namespace":"<somenamespace>"} - must allow access to any pod in <somenamespace> namespace.
- [x] Verify support for * wildcards - <some-name>-* and regex for name and namespace fields.
- [x] Verify support for delete pods collection - must use go-client.
[x] Verify scenarios with multiple roles defining kubernetes_resources:
- [x] Validate that the returned list of pods is the union of every role.
- [x] Validate that access to other pods is denied by RBAC.
- [x] Validate that the Kubernetes Groups/Users are correctly selected depending on the role that applies to the pod.
  - [x] Test with a kubernetes_groups that denies exec into a pod
[x] Verify the following scenarios for Resource Access Requests to Pods:
- [x] Create a valid resource access request and validate if access to other pods is denied.
- [x] Validate if creating a resource access request with Kubernetes resources denied by search_as_roles is not allowed.

Teleport with FIPS mode @r0mant

[x] Perform trusted clusters, Web and SSH sanity check with all teleport components deployed in FIPS mode.

ACME @mdwn

[x] Teleport can fetch TLS certificate automatically using ACME protocol.

Migrations @r0mant @zmb3

[x] Migrate trusted clusters from 2.4.0 to 2.5.0
- [x] Migrate auth server on main cluster, then rest of the servers on main cluster SSH should work for both main and old clusters
- [x] Migrate auth server on remote cluster, then rest of the remote cluster SSH should work

Command Templates

When interacting with a cluster, the following command templates are useful:

OpenSSH

# when connecting to the recording proxy, `-o 'ForwardAgent yes'` is required.
ssh -o "ProxyCommand ssh -o 'ForwardAgent yes' -p 3023 %r@proxy.example.com -s proxy:%h:%p" \
  node.example.com

# the above command only forwards the agent to the proxy, to forward the agent
# to the target node, `-o 'ForwardAgent yes'` needs to be passed twice.
ssh -o "ForwardAgent yes" \
  -o "ProxyCommand ssh -o 'ForwardAgent yes' -p 3023 %r@proxy.example.com -s proxy:%h:%p" \
  node.example.com

# when connecting to a remote cluster using OpenSSH, the subsystem request is
# updated with the name of the remote cluster.
ssh -o "ProxyCommand ssh -o 'ForwardAgent yes' -p 3023 %r@proxy.example.com -s proxy:%h:%p@foo.com" \
  node.foo.com

Teleport

# when connecting to a OpenSSH node, remember `-p 22` needs to be passed.
tsh --proxy=proxy.example.com --user=<username> --insecure ssh -p 22 node.example.com

# an agent can be forwarded to the target node with `-A`
tsh --proxy=proxy.example.com --user=<username> --insecure ssh -A -p 22 node.example.com

# the --cluster flag is used to connect to a node in a remote cluster.
tsh --proxy=proxy.example.com --user=<username> --insecure ssh --cluster=foo.com -p 22 node.foo.com

Teleport with SSO Providers @camscale

[x] Azure Active Directory (AD) install instructions work
- [ ] Azure Active Directory (AD) Screenshots are up-to-date
[x] ActiveDirectory (ADFS) install instructions work
- [x] Active Directory (ADFS) Screenshots are up-to-date
[x] Google Workspace install instructions work @AntonAM
- [x] Google Workspace Screenshots are up-to-date
[x] GitLab install instructions work @capnspacehook
- [x] GitLab Screenshots are up-to-date
[x] OneLogin install instructions work
- [x] OneLogin Screenshots are up-to-date
[x] OIDC install instructions work
- [x] OIDC Screenshots are up-to-date
[x] Okta install instructions work
- [x] Okta Screenshots are up-to-date
[x] All providers with guides in docs are covered in this test plan

GitHub External SSO @Tener

[x] Teleport OSS
- [x] GitHub organization without external SSO succeeds
- [x] GitHub organization with external SSO fails
[x] Teleport Enterprise
- [x] GitHub organization without external SSO succeeds
- [x] GitHub organization with external SSO succeeds

`tctl sso` family of commands @Tener

For help with setting up sso connectors, check out the Quick GitHub/SAML/OIDC Setup Tips

tctl sso configure helps to construct a valid connector definition:

[x] tctl sso configure github ... creates valid connector definitions
[x] tctl sso configure oidc ... creates valid connector definitions
[x] tctl sso configure saml ... creates valid connector definitions

tctl sso test test a provided connector definition, which can be loaded from file or piped in with tctl sso configure or tctl get --with-secrets. Valid connectors are accepted, invalid are rejected with sensible error messages.

[x] Connectors can be tested with tctl sso test.
- [x] GitHub
- [x] SAML
- [x] OIDC
  - [x] Google Workspace
  - [x] Non-Google IdP

Teleport Plugins @greedy52

[x] Test receiving a message via Teleport Slackbot
[x] Test receiving a new Jira Ticket via Teleport Jira

AWS Node Joining @gabrielcorado

Docs

[x] On EC2 instance with ec2:DescribeInstances permissions for local account: TELEPORT_TEST_EC2=1 go test ./integration -run TestEC2NodeJoin
[x] On EC2 instance with any attached role: TELEPORT_TEST_EC2=1 go test ./integration -run TestIAMNodeJoin
[x] EC2 Join method in IoT mode with node and auth in different AWS accounts
[x] IAM Join method in IoT mode with node and auth in different AWS accounts

Kubernetes Node Joining @gabrielcorado

[x] Join a Teleport node running in the same Kubernetes cluster via a Kubernetes ProvisionToken

Cloud Labels @GavinFrazar

[x] Create an EC2 instance with tags in instance metadata enabled and with tag foo: bar. Verify that a node running on the instance has label aws/foo=bar.
[x] Create an Azure VM with tag foo: bar. Verify that a node running on the instance has label azure/foo=bar.

Passwordless @codingllama

This feature has additional build requirements, so it should be tested with a pre-release build from Drone (eg: https://get.gravitational.com/teleport-v10.0.0-alpha.2-linux-amd64-bin.tar.gz).

This sections complements "Users -> Managing MFA devices". tsh binaries for each operating system (Linux, macOS and Windows) must be tested separately for FIDO2 items.

[x] Diagnostics

Commands should pass all tests.
- [x] tsh fido2 diag (macOS/Linux)
- [x] tsh touchid diag (macOS only)
- [x] tsh webauthnwin diag (Windows only)
[x] Registration
- [x] Register a passworldess FIDO2 key (tsh mfa add, choose WEBAUTHN and passwordless)
- [x] macOS/Linux
- [x] Windows
- [x] Register a platform authenticator
- [x] Touch ID credential (tsh mfa add, choose TOUCHID)
- [x] Windows hello credential (tsh mfa add, choose WEBAUTHN and passwordless)
[x] Login
- [x] Passwordless login using FIDO2 (tsh login --auth=passwordless)
- [x] macOS/Linux
- [x] Windows
- [x] Passwordless login using platform authenticator (tsh login --auth=passwordless)
- [x] Touch ID
- [x] Windows Hello
- [x] tsh login --auth=passwordless --mfa-mode=cross-platform uses FIDO2
- [x] macOS/Linux
- [x] Windows
- [x] tsh login --auth=passwordless --mfa-mode=platform uses platform authenticator
- [x] Touch ID
- [x] Windows Hello
- [x] tsh login --auth=passwordless --mfa-mode=auto prefers platform authenticator
- [x] Touch ID
- [x] Windows Hello
- [x] Passwordless disable switch works (auth_service.authentication.passwordless = false)
- [x] Cluster in passwordless mode defaults to passwordless (auth_service.authentication.connector_name = passwordless)
- [x] Cluster in passwordless mode allows MFA login (tsh login --auth=local)
[x] Touch ID support commands
- [x] tsh touchid ls works
- [x] tsh touchid rm works (careful, may lock you out!)

Device Trust @sfreiberg

Device Trust requires Teleport Enterprise.

This feature has additional build requirements, so it should be tested with a pre-release build from Drone (eg: https://get.gravitational.com/teleport-v10.0.0-alpha.2-linux-amd64-bin.tar.gz).

Client-side enrollment requires a signed tsh for macOS, make sure to use the tsh binary from tsh.app.

A simple formula for testing device authorization is:

# Before enrollment.
# Replace with other kinds of access, as appropriate (db, kube, etc)
tsh ssh node-that-requires-device-trust
> ERROR: ssh: rejected: administratively prohibited (unauthorized device)
# Register the device.
# Get the serial number from "Apple -> About This Mac".
tctl devices add --os=macos --asset-tag=<SERIAL_NUMBER> --enroll
# Enroll the device.
tsh device enroll --token=<TOKEN_FROM_COMMAND_ABOVE>
tsh logout; tsh login
# After enrollment
tsh ssh node-that-requires-device-trust
> $

[ ] Inventory management
- [x] Add device (tctl devices add)
- [x] Add device and create enrollment token (tctl devices add --enroll)
- [x] List devices (tctl devices ls)
- [x] Remove device using device ID (tctl devices rm)
- [x] Remove device using asset tag (tctl devices rm)
- [x] Create enrollment token using device ID (tctl devices enroll)
- [x] Create enrollment token using asset tag (tctl devices enroll)

[x] Device enrollment

[x] Enroll device on macOS (tsh device enroll)
[x] Verify device extensions on TLS certificate

Note that different accesses have different certificates (Database, Kube, etc).

$ openssl x509 -noout -in ~/.tsh/keys/zarquon/llama-x509.pem -nameopt sep_multiline -subject | grep 1.3.9999.3
> 1.3.9999.3.1=6e60b9fd-1e3e-473d-b148-27b4f158c2a7
> 1.3.9999.3.2=AAAAAAAAAAAA
> 1.3.9999.3.3=661c9340-81b0-4a1a-a671-7b1304d28600

[x] Verify device extensions on SSH certificate

ssh-keygen -L -f ~/.tsh/keys/zarquon/llama-ssh/zarquon-cert.pub | grep teleport-device-
teleport-device-asset-tag ...
teleport-device-credential-id ...
teleport-device-id ...

[x] Device authorization
- [x] device_trust.mode other than "off" or "" not allowed (OSS)
- [x] device_trust.mode="off" doesn't impede access (Enterprise and OSS)
- [x] device_trust.mode="optional" doesn't impede access, but issues device extensions on login
- [x] device_trust.mode="required" enforces enrolled devices
- [x] device_trust.mode="required" is enforced by processes, and not only by Auth APIs
Testing this requires issuing a certificate without device extensions (mode="off"), then changing the cluster configuration to mode="required" and attempting to access a process directly, without a login attempt.
- [x] Device authorization works correctly for both require_session_mfa=false and require_session_mfa=true
- [x] Device authorization applies to SSH access (all items above)
- [x] Device authorization applies to Trusted Clusters (root with mode="optional" and leaf with mode="required")
- [x] Device authorization applies to Database access (all items above) @smallinsky
- [x] Device authorization applies to Kubernetes access (all items above) @tigrato
[x] Device audit (see lib/events/codes.go)
- [x] Inventory management actions issue events (success only)
- [x] Device enrollment issues device event (any outcomes)
- [x] Device authorization issues device event (any outcomes)
- [x] Events with UserMetadata contain TrustedDevice data (for certificates with device extensions)

Hardware Key Support @Joerger

Hardware Key Support is an Enterprise feature and is not available for OSS.

You will need a YubiKey 4.3+ to test this feature.

This feature has additional build requirements, so it should be tested with a pre-release build from Drone (eg: https://get.gravitational.com/teleport-ent-v11.0.0-alpha.2-linux-amd64-bin.tar.gz).

Server Access @Joerger

These tests should be carried out sequentially. tsh tests should be carried out on Linux, MacOS, and Windows.

[x] tsh login as user with Webauthn login and no hardware key requirement.
[x] Request a role with role.role_options.require_session_mfa: hardware_key - tsh login --request-roles=hardware_key_required
- [x] Assuming the role should force automatic re-login with yubikey
- [x] tsh ssh
- [x] Requires yubikey to be connected for re-login
- [x] Prompts for per-session MFA
[x] Request a role with role.role_options.require_session_mfa: hardware_key_touch - tsh login --request-roles=hardware_key_touch_required
- [x] Assuming the role should force automatic re-login with yubikey
- [x] Prompts for touch if not cached (last touch within 15 seconds)
- [x] tsh ssh
- [x] Requires yubikey to be connected for re-login
- [x] Prompts for touch if not cached
[x] tsh logout and tsh login as the user with no hardware key requirement.
[x] Upgrade auth settings to auth_service.authentication.require_session_mfa: hardware_key
- [x] Using the existing login session (tsh ls) should force automatic re-login with yubikey
- [x] tsh ssh
- [x] Requires yubikey to be connected for re-login
- [x] Prompts for per-session MFA
[x] Upgrade auth settings to auth_service.authentication.require_session_mfa: hardware_key_touch
- [x] Using the existing login session (tsh ls) should force automatic re-login with yubikey
- [x] Prompts for touch if not cached
- [x] tsh ssh
- [x] Requires yubikey to be connected for re-login
- [x] Prompts for touch if not cached

Other @GavinFrazar

Set auth_service.authentication.require_session_mfa: hardware_key_touch in your cluster auth settings.

[x] Database Acces: tsh proxy db
[x] Application Access: tsh login app && tsh proxy app

Performance @rosstimothy @fspmarshall

Perform all tests on the following configurations:

[x] With default networking configuration
[x] With Proxy Peering Enabled
[ ] With TLS Routing Enabled
Cluster with 10K direct dial nodes:
- [x] etcd
- [x] DynamoDB
- [ ] Firestore
Cluster with 10K reverse tunnel nodes:
- [x] etcd
- [x] DynamoDB
- [ ] Firestore
Cluster with 500 trusted clusters:
[x] etcd
[x] DynamoDB
[ ] Firestore

Soak Test @rosstimothy @fspmarshall

Run 30 minute soak test with a mix of interactive/non-interactive sessions for both direct and reverse tunnel nodes:

tsh bench --duration=30m user@direct-dial-node ls
tsh bench -i --duration=30m user@direct-dial-node ps uax

tsh bench --duration=30m user@reverse-tunnel-node ls
tsh bench -i --duration=30m user@reverse-tunnel-node ps uax

Observe prometheus metrics for goroutines, open files, RAM, CPU, Timers and make sure there are no leaks

[x] Verify that prometheus metrics are accurate.

Concurrent Session Test

Cluster with 1k reverse tunnel nodes

Run a concurrent session test that will spawn 5 interactive sessions per node in the cluster:

tsh bench sessions --max=5000 user ls
tsh bench sessions --max=5000 --web user ls

[x] Verify that all 5000 sessions are able to be established.
[x] Verify that tsh and the web UI are still functional.

Robustness @rosstimothy @fspmarshall

Connectivity Issues:
[x] Verify that a lack of connectivity to Auth does not prevent access to resources which do not require a moderated session and in async recording mode from an already issued certificate.
[x] Verify that a lack of connectivity to Auth prevents access to resources which require a moderated session and in async recording mode from an already issued certificate.

Teleport with Cloud Providers @hugoShaka

AWS @hugoShaka

[x] Deploy Teleport to AWS. Using DynamoDB & S3
[x] Deploy Teleport Enterprise to AWS. Using HA Setup https://gravitational.com/teleport/docs/aws-terraform-guide/

GCP @hugoShaka

[x] Deploy Teleport to GCP. Using Cloud Firestore & Cloud Storage
[x] Deploy Teleport to GKE. Google Kubernetes engine.
[x] Deploy Teleport Enterprise to GCP.

IBM @hugoShaka

[ ] Deploy Teleport to IBM Cloud. Using IBM Database for etcd & IBM Object Store
[x] Deploy Teleport to IBM Cloud Kubernetes.
[x] Deploy Teleport Enterprise to IBM Cloud.

Application Access @mdwn

[x] Run an application within local cluster.
- [x] Verify the debug application debug_app: true works.
- [x] Verify an application can be configured with command line flags.
- [x] Verify an application can be configured from file configuration.
- [x] Verify that applications are available at auto-generated addresses name.rootProxyPublicAddr and well as publicAddr.
[x] Run an application within a trusted cluster.
- [x] Verify that applications are available at auto-generated addresses name.rootProxyPublicAddr.
[x] Verify Audit Records.
- [x] app.session.start and app.session.chunk events are created in the Audit Log.
- [x] app.session.chunk points to a 5 minute session archive with multiple app.session.request events inside.
- [x] tsh play <chunk-id> can fetch and print a session chunk archive.
[x] Verify JWT using verify-jwt.go.
[x] Verify RBAC.
[x] Verify CLI access with tsh app login.
[x] Verify AWS console access.
- [x] Can log into AWS web console through the web UI.
- [x] Can interact with AWS using tsh aws commands.
[x] Verify Azure CLI access with tsh app login.
- [x] Can interact with Azure using tsh az commands.
- [x] Can interact with Azure using a combination of tsh proxy az and az commands.
[x] Verify GCP CLI access with tsh app login.
- [x] Can interact with GCP using tsh gcloud commands.
- [x] Can interact with Google Cloud Storage using tsh gsutil commands.
- [x] Can interact with GCP/GCS using a combination of tsh proxy gcloud and gcloud/gsutil commands.
[x] Verify dynamic registration.
- [x] Can register a new app using tctl create.
- [x] Can update registered app using tctl create -f.
- [x] Can delete registered app using tctl rm.
[x] Test Applications screen in the web UI (tab is located on left side nav on dashboard):
- [x] Verify that all apps registered are shown
- [x] Verify that clicking on the app icon takes you to another tab
- [x] Verify using the bash command produced from Add Application dialogue works (refresh app screen to see it registered)

Database Access @smallinsky

[x] Connect to a database within a local cluster.
- [x] Self-hosted Postgres. @GavinFrazar
- [x] Self-hosted MySQL. @Tener
- [x] Self-hosted MariaDB. @Tener
- [x] Self-hosted MongoDB. @GavinFrazar
- [x] Self-hosted CockroachDB. @Tener
- [x] Self-hosted Redis. @greedy52
- [x] Self-hosted Redis Cluster. @greedy52
- [x] Self-hosted MSSQL. @gabrielcorado
- [x] AWS Aurora Postgres. @greedy52
- [x] AWS Aurora MySQL. @greedy52
- [x] AWS RDS Proxy (MySQL, Postgres, or MariaDB) @smallinsky
- [x] AWS Redshift. @gabrielcorado
- [x] AWS Redshift Serverless. @gabrielcorado
- [x] AWS ElastiCache. @greedy52
- [x] AWS MemoryDB. @greedy52
- [x] GCP Cloud SQL Postgres. @gabrielcorado
- [x] GCP Cloud SQL MySQL. @gabrielcorado
- [x] Snowflake. @smallinsky
- [x] Azure Cache for Redis. @GavinFrazar
- [x] Azure single-server MySQL and Postgres @smallinsky
- [x] Azure flexible-server MySQL and Postgres @smallinsky
- [x] Elasticsearch. @Tener
- [x] Cassandra/ScyllaDB. @gabrielcorado
- [x] Dynamodb. @greedy52
- [x] Azure SQL Server. @gabrielcorado
[x] Connect to a database within a remote cluster via a trusted cluster.
- [x] Self-hosted Postgres. @GavinFrazar
- [x] Self-hosted MySQL. @Tener
- [x] Self-hosted MariaDB. @Tener
- [x] Self-hosted MongoDB. @GavinFrazar
- [x] Self-hosted CockroachDB. @GavinFrazar
- [x] Self-hosted Redis. @greedy52
- [x] Self-hosted Redis Cluster. @greedy52
- [x] Self-hosted MSSQL. @gabrielcorado
- [x] AWS Aurora Postgres. @greedy52
- [x] AWS Aurora MySQL. @greedy52
- [x] AWS RDS Proxy (MySQL, Postgres, or MariaDB) @smallinsky
- [x] AWS Redshift. @gabrielcorado
- [x] AWS Redshift Serverless. @gabrielcorado
- [x] AWS ElastiCache. @greedy52
- [x] AWS MemoryDB. @greedy52
- [x] GCP Cloud SQL Postgres. @gabrielcorado
- [x] GCP Cloud SQL MySQL. @gabrielcorado
- [x] Snowflake. @smallinsky @smallinsky
- [x] Azure Cache for Redis. @GavinFrazar
- [x] Azure single-server MySQL and Postgres @smallinsky
- [x] Azure flexible-server MySQL and Postgres @smallinsky
- [x] Elasticsearch. @Tener
- [x] Cassandra/ScyllaDB. @gabrielcorado
- [x] Dynamodb. @greedy52
- [x] Azure SQL Server. @gabrielcorado
[x] Verify audit events. @GavinFrazar
- [x] db.session.start is emitted when you connect.
- [x] db.session.end is emitted when you disconnect.
- [x] db.session.query is emitted when you execute a SQL query.
[x] Verify RBAC. @gabrielcorado
- [x] tsh db ls shows only databases matching role's db_labels.
- [x] Can only connect as users from db_users.
- [x] (Postgres only) Can only connect to databases from db_names.
- [x] db.session.start is emitted when connection attempt is denied.
- [x] (MongoDB only) Can only execute commands in databases from db_names.
- [x] db.session.query is emitted when command fails due to permissions.
- [x] Can configure per-session MFA. @GavinFrazar
- [x] MFA tap is required on each tsh db connect.
[x] Verify dynamic registration. @GavinFrazar
- [x] Can register a new database using tctl create.
- [x] Can update registered database using tctl create -f.
- [x] Can delete registered database using tctl rm.
[x] Verify discovery.
- [x] AWS @greedy52
  - [x] Can detect and register RDS instances.
  - [x] Can detect and register Aurora clusters, and their reader and custom endpoints.
  - [x] Can detect and register RDS proxies, and their custom endpoints.
  - [x] Can detect and register Redshift clusters.
  - [x] Can detect and register Redshift serverless workgroups, and their VPC endpoints.
  - [x] Can detect and register ElastiCache Redis clusters.
  - [x] Can detect and register MemoryDB clusters.
- [x] Azure @GavinFrazar
  - [x] Can detect and register MySQL and Postgres single-server instances.
  - [x] Can detect and register MySQL and Postgres flexible-server instances.
  - [x] Can detect and register Azure Cache for Redis servers.
  - [x] Can detect and register Azure SQL Servers and Azure SQL Managed Instances.
[x] Verify Teleport managed users (password rotation, auto 'auth' on connection, etc.). @greedy52
- [x] Can detect and manage ElastiCache users
- [x] Can detect and manage MemoryDB users
[x] Test Databases screen in the web UI (tab is located on left side nav on dashboard): @smallinsky
- [x] Verify that all dbs registered are shown with correct name, description, type, and labels
- [x] Verify that clicking on a rows connect button renders a dialogue on manual instructions with Step 2 login value matching the rows name column
- [x] Verify searching for all columns in the search bar works
- [x] Verify you can sort by all columns except labels
[x] Other
- [x] MySQL server version reported by Teleport is correct. @smallinsky

TLS Routing @smallinsky

[x] Verify that teleport proxy v2 configuration starts only a single listener. @Tener

version: v2
teleport:
proxy_service:
  enabled: "yes"
  public_addr: ['root.example.com']
  web_listen_addr: 0.0.0.0:3080

[x] Run Teleport Proxy in multiplex mode auth_service.proxy_listener_mode: "multiplex" @Tener
- [x] Trusted cluster
- [x] Setup trusted clusters using single port setup web_proxy_addr == tunnel_addr
```
kind: trusted_cluster
spec:
...
web_proxy_addr: root.example.com:443
tunnel_addr: root.example.com:443
...
```
[x] Database Access
- [x] Verify that tsh db connect works through proxy running in multiplex mode
- [x] Postgres @GavinFrazar
- [x] MySQL @Tener
- [x] MariaDB @Tener
- [x] MongoDB @GavinFrazar
- [x] CockroachDB @Tener
- [x] Redis @greedy52
- [x] MSSQL @gabrielcorado
- [x] Snowflake @smallinsky
- [x] Elasticsearch. @greedy52
- [x] Cassandra/ScyllaDB. @gabrielcorado
- [x] Verify connecting to a database through TLS ALPN SNI local proxy tsh db proxy with a GUI client. @greedy52 @GavinFrazar @smallinsky @Tener
- [x] Verify tsh proxy db with teleport proxy behind ALB. @greedy52
[x] Application Access @smallinsky
- [x] Verify app access through proxy running in multiplex mode
[x] SSH Access @gabrielcorado
- [x] Connect to a OpenSSH server through a local ssh proxy ssh -o "ForwardAgent yes" -o "ProxyCommand tsh proxy ssh" user@host.example.com
- [x] Connect to a OpenSSH server on leaf-cluster through a local ssh proxyssh -o "ForwardAgent yes" -o "ProxyCommand tsh proxy ssh --user=%r --cluster=leaf-cluster %h:%p" user@node.foo.com
- [x] Verify tsh ssh access through proxy running in multiplex mode
[x] Kubernetes access: @Tener
- [x] Verify kubernetes access through proxy running in multiplex mode

Desktop Access @ibeckermayer

Direct mode (set listen_addr):
- [x] Can connect to desktop defined in static hosts section.
- [x] Can connect to desktop discovered via LDAP
IoT mode (reverse tunnel through proxy):
- [x] Can connect to desktop defined in static hosts section.
- [x] Can connect to desktop discovered via LDAP
[x] Connect multiple windows_desktop_services to the same Teleport cluster, verify that connections to desktops on different AD domains works. (Attempt to connect several times to verify that you are routed to the correct windows_desktop_service)
Verify user input
- [x] Download Keyboard Key Info and verify all keys are processed correctly in each supported browser. Known issues: F11 cannot be captured by the browser without special configuration on MacOS.
- [x] Left click and right click register as Windows clicks. (Right click on the desktop should show a Windows menu, not a browser context menu)
- [x] Vertical and horizontal scroll work. Horizontal Scroll Test
Locking
- [x] Verify that placing a user lock terminates an active desktop session.
- [x] Verify that placing a desktop lock terminates an active desktop session.
- [x] Verify that placing a role lock terminates an active desktop session.
Labeling
- [x] Set client_idle_timeout to a small value and verify that idle sessions are terminated (the session should end and an audit event will confirm it was due to idle connection)
- [x] All desktops have teleport.dev/origin label.
- [x] Dynamic desktops have additional teleport.dev labels for OS, OS Version, DNS hostname.
- [x] Regexp-based host labeling applies across all desktops, regardless of origin.
RBAC
- [x] RBAC denies access to a Windows desktop due to labels
- [x] RBAC denies access to a Windows desktop with the wrong OS-login.
Clipboard Support
- When a user has a role with clipboard sharing enabled and is using a chromium based browser
- [x] Going to a desktop when clipboard permissions are in "Ask" mode (aka "prompt") causes the browser to show a prompt when you first click or press a key
- [x] The clipboard icon is highlighted in the top bar
- [x] After allowing clipboard permission, copy text from local workstation, paste into remote desktop
- [x] After allowing clipboard permission, copy text from remote desktop, paste into local workstation
- [x] After disallowing clipboard permission, confirm copying text from local workstation and pasting into remote desktop doesn't work
- [x] After disallowing clipboard permission, confirm copying text from remote desktop and pasting into local workstation doesn't work
- When a user has a role with clipboard sharing enabled and is not using a chromium based browser
- [x] The clipboard icon is not highlighted in the top bar and copy/paste does not work
- When a user has a role with clipboard sharing disabled and is using a chromium and non-chromium based browser (confirm both)
- [x] The clipboard icon is not highlighted in the top bar and copy/paste does not work
Directory Sharing
- On supported, non-chromium based browsers (Firefox/Safari)
- [x] Attempting to share directory logs a sensible warning in the warning dropdown
- On supported, chromium based browsers (Chrome/Edge)
- Begin sharing works
  - [x] The shared directory icon in the top right of the screen is highlighted when directory sharing is initiated
  - [x] The shared directory appears as a network drive named " on teleport"
  - [x] The share directory menu option disappears from the menu
- Navigation
  - [x] The folders of the shared directory are navigable (move up and down the directory tree)
- CRUD
  - [x] A new text file can be created
  - [x] The text file can be written to (saved)
  - [x] The text file can be read (close it, check that it's saved on the local machine, then open it again on the remote)
  - [x] The text file can be deleted
- File/Folder movement
  - In to out (make at least one of these from a non-top-level-directory)
  - [x] A file from inside the shared directory can be drag-and-dropped outside the shared directory
  - [x] A folder from inside the shared directory can be drag-and-dropped outside the shared directory (and its contents retained)
  - [x] A file from inside the shared directory can be cut-pasted outside the shared directory
  - [x] A folder from inside the shared directory can be cut-pasted outside the shared directory
  - [x] A file from inside the shared directory can be copy-pasted outside the shared directory
  - [x] A folder from inside the shared directory can be copy-pasted outside the shared directory
  - Out to in (make at least one of these overwrite an existing file, and one go into a non-top-level directory)
  - [x] A file from outside the shared directory can be drag-and-dropped into the shared directory
  - [x] A folder from outside the shared directory can be drag-and-dropped into the shared directory (and its contents retained)
  - [x] A file from outside the shared directory can be cut-pasted into the shared directory
  - [x] A folder from outside the shared directory can be cut-pasted into the shared directory
  - [x] A file from outside the shared directory can be copy-pasted into the shared directory
  - [x] A folder from outside the shared directory can be copy-pasted into the shared directory
  - Within
  - [x] A file from inside the shared directory cannot be drag-and-dropped to another folder inside the shared directory: a dismissible "Unsupported Action" dialog is shown
  - [x] A folder from inside the shared directory cannot be drag-and-dropped to another folder inside the shared directory: a dismissible "Unsupported Action" dialog is shown
  - [x] A file from inside the shared directory cannot be cut-pasted to another folder inside the shared directory: a dismissible "Unsupported Action" dialog is shown
  - [x] A folder from inside the shared directory cannot be cut-pasted to another folder inside the shared directory: a dismissible "Unsupported Action" dialog is shown
  - [x] A file from inside the shared directory can be copy-pasted to another folder inside the shared directory
  - [x] A folder from inside the shared directory can be copy-pasted to another folder inside shared directory (and its contents retained)
- RBAC
- [x] Give the user one role that explicitly disables directory sharing (desktop_directory_sharing: false) and confirm that the option to share a directory doesn't appear in the menu
Per-Session MFA (try webauthn on each of Chrome, Safari, and Firefox; u2f only works with Firefox)
- [x] Attempting to start a session no keys registered shows an error message
- [x] Attempting to start a session with a webauthn registered pops up the "Verify Your Identity" dialog
- [x] Hitting "Cancel" shows an error message
- [x] Hitting "Verify" causes your browser to prompt you for MFA
- [x] Cancelling that browser MFA prompt shows an error
- [x] Successful MFA verification allows you to connect
Session Recording
- [x] Verify sessions are not recorded if all of a user's roles disable recording
- [x] Verify sync recording (mode: node-sync or mode: proxy-sync)
- [x] Verify async recording (mode: node or mode: proxy)
- [x] Sessions show up in session recordings UI with desktop icon
- [x] Sessions can be played back, including play/pause functionality
- [x] Sessions playback speed can be toggled while its playing
- [x] Sessions playback speed can be toggled while its paused
- [x] A session that ends with a TDP error message can be played back, ends by displaying the error message, and the progress bar progresses to the end.
- [x] Attempting to play back a session that doesn't exist (i.e. by entering a non-existing session id in the url) shows a relevant error message.
- [x] RBAC for sessions: ensure users can only see their own recordings when using the RBAC rule from our docs
Audit Events (check these after performing the above tests)
- [x] windows.desktop.session.start (TDP00I) emitted on start
- [x] windows.desktop.session.start (TDP00W) emitted when session fails to start (due to RBAC, for example)
- [x] client.disconnect (T3006I) emitted when session is terminated by or fails to start due to lock
- [x] windows.desktop.session.end (TDP01I) emitted on end
- [x] desktop.clipboard.send (TDP02I) emitted for local copy -> remote paste
- [x] desktop.clipboard.receive (TDP03I) emitted for remote copy -> local paste
- [x] desktop.directory.share (TDP04I) emitted when Teleport starts sharing a directory
- [x] desktop.directory.read (TDP05I) emitted when a file is read over the shared directory
- [x] desktop.directory.write (TDP06I) emitted when a file is written to over the shared directory
Warnings/Errors
- [x] Induce the backend to send a TDP Notification of severity warning (1), confirm that a warning is logged in the warning dropdown
- [x] Induce the backend to send a TDP Notification of severity error (2), confirm that session is terminated and error popup is shown
- [x] Induce the backend to send a TDP Error, confirm that session is terminated and error popup is shown (confirms backwards compatibility w/ older w_d_s starting in Teleport 12)
Trusted Cluster / Tunneling
- Set up Teleport in a trusted cluster configuration where the root and leaf cluster has a w_d_s connected via tunnel (w_d_s running as a separate process)
- [x] Confirm that windows desktop sessions can be made on root cluster
- [x] Confirm that windows desktop sessions can be made on leaf cluster

Binaries compatibility @tobiaszheller

Verify tsh runs on:
- [x] Windows 10
- [x] MacOS

Machine ID @timothyb89

SSH

With a default Teleport instance configured with a SSH node:

[x] Verify you are able to create a new bot user with tctl bots add robot --roles=access. Follow the instructions provided in the output to start tbot
[x] Verify you are able to connect to the SSH node using openssh with the generated ssh_config in the destination directory
[x] Verify that after the renewal period (default 20m, but this can be reduced via configuration), that newly generated certificates are placed in the destination directory
[x] Verify that sending both SIGUSR1 and SIGHUP to a running tbot process causes a renewal and new certificates to be generated
[x] Verify that you are able to make a connection to the SSH node using the ssh_config provided by tbot after each phase of a manual CA rotation.

Ensure the above tests are completed for both:

[x] Directly connecting to the auth server
[x] Connecting to the auth server via the proxy reverse tunnel

DB Access

With a default Postgres DB instance, a Teleport instance configured with DB access and a bot user configured:

[x] Verify you are able to connect to and interact with a database using tbot db while tbot start is running

Host users creation @lxea

Host users creation docs Host users creation RFD

Verify host users creation functionality
- [x] non-existing users are created automatically
- [x] users are added to groups
- [x] non-existing configured groups are created
- [x] created users are added to the teleport-system group
- [x] users are cleaned up after their session ends
- [x] cleanup occurs if a program was left running after session ends
- [x] sudoers file creation is successful
- [x] Invalid sudoers files are not created
- [x] existing host users are not modified
- [x] setting disable_create_host_user: true stops user creation from occurring

CA rotations @espadolini

Verify the CA rotation functionality itself (by checking in the backend or with tctl get cert_authority)
- [x] standby phase: only active_keys, no additional_trusted_keys
- [x] init phase: active_keys and additional_trusted_keys
- [x] update_clients and update_servers phases: the certs from the init phase are swapped
- [x] standby phase: only the new certs remain in active_keys, nothing in additional_trusted_keys
- [x] rollback phase (second pass, after completing a regular rotation): same content as in the init phase
- [x] standby phase after rollback: same content as in the previous standby phase
Verify functionality in all phases (clients might have to log in again in lieu of waiting for credentials to expire between phases)
- [x] SSH session in tsh from a previous phase
- [x] SSH session in web UI from a previous phase
- [x] New SSH session with tsh
- [x] New SSH session with web UI
- [x] New SSH session in a child cluster on the same major version
- [x] New SSH session in a child cluster on the previous major version
- [x] New SSH session from a parent cluster
- [x] Application access through a browser
- [x] Application access through curl with tsh app login
- [x] kubectl get po after tsh kube login
- [x] Database access (no configuration change should be necessary if the database CA isn't rotated, other Teleport functionality should not be affected if only the database CA is rotated)

EC2 Discovery @lxea

EC2 Discovery docs

Verify EC2 instance discovery
- [x] Only EC2 instances matching given AWS tags have the installer executed on them
- [x] Only the IAM permissions mentioned in the discovery docs are required for operation
- [x] Custom scripts specified in different matchers are executed
- [x] Custom SSM documents specified in different matchers are executed
- [x] New EC2 instances with matching AWS tags are discovered and added to the teleport cluster
- [x] Large numbers of EC2 instances (51+) are all successfully added to the cluster
- [x] Nodes that have been discovered do not have the install script run on the node multiple times

Documentation @ptgott @alexfornuto

Checks should be performed on the version of documentation corresponding to the major release we're testing for. For example, for Teleport 12 release use branch/v12 branch and make sure to select "Version 12.0" in the documentation version switcher.

[x] Verify installation instructions are accurate:
- [x] Self-hosted: https://goteleport.com/docs/installation (@alexfornuto )
- [x] Cloud: https://goteleport.com/docs/deploy-a-cluster/teleport-cloud/downloads/?scope=cloud (@ptgott )
[x] Verify getting started instructions are accurate:
- [x] OSS: https://goteleport.com/docs/deploy-a-cluster/open-source/ @alexfornuto
- [x] Enterprise: https://goteleport.com/docs/deploy-a-cluster/teleport-enterprise/getting-started/?scope=enterprise @alexfornuto
- [x] Cloud: https://goteleport.com/docs/deploy-a-cluster/teleport-cloud/introduction/?scope=cloud @ptgott
- [x] Helm: https://goteleport.com/docs/deploy-a-cluster/helm-deployments/kubernetes-cluster/?scope=enterprise @ptgott
[ ] Verify upcoming releases page is accurate:
- [x] https://goteleport.com/docs/preview/upcoming-releases/?scope=enterprise (PRs here: https://github.com/gravitational/teleport/pulls?q=is%3Apr+is%3Aopen+upcoming+releases)
- [ ] Only exists for the default docs version. (@alexfornuto )
[ ] Verify Teleport versions throughout documentation are correct and reflect upcoming release: (@alexfornuto )
[x] Verify that all necessary documentation for the release was backported to release branch: (@alexfornuto )
- [x] Diff between master and release branch and make sure there are no missed PRs
[x] Verify deprecated Teleport versions are added to the older versions page: See gravitational/docs#222
- [x] https://goteleport.com/docs/older-versions/
[x] Verify gravitational/docs version configuration (@ptgott ): See gravitational/docs#222
- [x] Verify latest version in gravitational/docs/config.json
- [x] Verify gravitational/docs/.gitmodules contains latest release
[ ] Verify changelog is up-to-date and complete for the default docs version (@alexfornuto ):
- [ ] https://goteleport.com/docs/changelog/
[ ] Verify supported versions table in FAQ: https://github.com/gravitational/teleport/pull/20632
- [ ] https://goteleport.com/docs/faq/#supported-versions

Resources

Quick GitHub/SAML/OIDC Setup Tips

Tener commented 1 year ago

@mdwn I've added these points to the test plan, seemingly under your remit:

- [ ] Verify [Azure CLI access](https://goteleport.com/docs/ver/12.x/application-access/guides/azure/) with `tsh app login`.
  - [ ] Can interact with Azure using `tsh az` commands.
  - [ ] Can interact with Azure using a combination of `tsh proxy az` and `az` commands.
- [ ] Verify [GCP CLI access](https://github.com/gravitational/teleport/pull/19905) with `tsh app login`.
  - [ ] Can interact with GCP using `tsh gcloud` commands.
  - [ ] Can interact with Google Cloud Storage using `tsh gsutil` commands.
  - [ ] Can interact with GCP/GCS using a combination of `tsh proxy gcloud` and `gcloud`/`gsutil` commands.

Both Azure and GCP integrations are on master and will be part of the cut tomorrow. The PR for the GCP docs is in review https://github.com/gravitational/teleport/pull/19905, but slightly out of sync with the implementation; this will be corrected early next week. Please don't hesitate to ask me for any clarifications or tips.

I'll send PR updating the test plan template too.

GavinFrazar commented 1 year ago

I've added/edited these points to the test plan (for discovery and connect via local/remote cluster):

  - [ ] Azure single-server MySQL and Postgres
  - [ ] Azure flexible-server MySQL and Postgres

Added them to connect test because flexible server integration required an update to the way we modify db username in the engine.

Forgot to update the test plan template in #19759 I'll open a PR to update that template now as well.

espadolini commented 1 year ago

Added "Changing role map of existing Trusted Cluster" here and in #20325

tigrato commented 1 year ago

Added in #20274

hugoShaka commented 1 year ago

tctl does not default to local auth: https://github.com/gravitational/teleport/issues/20346

timothyb89 commented 1 year ago

Regression in tsh breaks identity file loading (affects most tbot proxying features, including ssh/db access): https://github.com/gravitational/teleport/issues/20373

and another small issue where tbot's ssh_config forgets nonstandard ports: https://github.com/gravitational/teleport/issues/20378

GavinFrazar commented 1 year ago

20384 issue with PIV yubikey integration

mdwn commented 1 year ago

AWS console is inaccessible via the Teleport UI: https://github.com/gravitational/teleport/issues/20385

tigrato commented 1 year ago

The default access role misses permissions to list pods #20401

codingllama commented 1 year ago

tsh login --auth=local uses platform passwordless if it can (#20429). Not a huge deal, as it does respect other settings/flags, but I'll take a look.

mdwn commented 1 year ago

Setting Azure identities doesn't work for all valid characters in an identity string: https://github.com/gravitational/teleport/issues/20434

hugoShaka commented 1 year ago

Helm chart deadlock: https://github.com/gravitational/teleport/pull/20488

GavinFrazar commented 1 year ago

teleport db configure create --azure-sqlserver-discovery=$region generates invalid config yaml. fix here: https://github.com/gravitational/teleport/pull/20496

codingllama commented 1 year ago

I've found some issues with device trust, unusual verbs (create_enroll_token and enroll) and RoleAdmin. Pushing patches soon. (FYI @sfreiberg.)

codingllama commented 1 year ago

I've found some issues with device trust, unusual verbs (create_enroll_token and enroll) and RoleAdmin. Pushing patches soon. (FYI @sfreiberg.)

Promised patches: #20505 and https://github.com/gravitational/teleport.e/pull/724. We'll need an e/ bump on branch/v12 after all is done.

codingllama commented 1 year ago

tctl devices rm issue: #20506

camscale commented 1 year ago

Okta SSO documentation setup issue: https://github.com/gravitational/teleport/issues/20538

rosstimothy commented 1 year ago

etcd Load Testing

Agent Mesh

Soak Test

----Direct Dial Node Test----
tsh --insecure --proxy=monster.gravitational.co:3080 -i /etc/teleport/auth bench --duration=30m root@node-6f44d86564-lqmrg ls

* Requests originated: 17999
* Requests failed: 0

Histogram

Percentile Response Duration
---------- -----------------
25         150 ms
50         152 ms
75         156 ms
90         160 ms
95         165 ms
99         191 ms
100        455 ms

----Reverse Tunnel Node Test----
tsh --insecure --proxy=monster.gravitational.co:3080 -i /etc/teleport/auth bench --duration=30m root@iot-node-86b9c86bff-fgrxs ls

* Requests originated: 17999
* Requests failed: 0

Histogram

Percentile Response Duration
---------- -----------------
25         146 ms
50         150 ms
75         154 ms
90         162 ms
95         170 ms
99         191 ms
100        411 ms

Proxy Peering

10k Tunnel Nodes

https://teleportcoreteam.grafana.net/goto/5i-Am-T4z?orgId=1

10k Direct Dial Nodes

https://teleportcoreteam.grafana.net/goto/cv55cFT4z?orgId=1

500 Trusted Cluster

https://teleportcoreteam.grafana.net/goto/Oog2Abo4z?orgId=1

Soak Test

----Direct Dial Node Test----
tsh --insecure --proxy=monster.gravitational.co:3080 -i /etc/teleport/auth bench --duration=30m root@node-6f44d86564-frcnx ls

* Requests originated: 17999
* Requests failed: 0

Histogram

Percentile Response Duration
---------- -----------------
25         147 ms
50         149 ms
75         153 ms
90         156 ms
95         160 ms
99         188 ms
100        352 ms

----Reverse Tunnel Node Test----
tsh --insecure --proxy=monster.gravitational.co:3080 -i /etc/teleport/auth bench --duration=30m root@iot-node-86b9c86bff-x4pbr ls

* Requests originated: 17999
* Requests failed: 0

Histogram

Percentile Response Duration
---------- -----------------
25         164 ms
50         169 ms
75         176 ms
90         186 ms
95         191 ms
99         209 ms
100        439 ms

ravicious commented 1 year ago

~teleport-ent macOS binaries are not signed.~ https://github.com/gravitational/teleport.e/issues/741

Edit: It turns out it's a known issue.

codingllama commented 1 year ago

App Access and require_session_mfa issue: #20634.

alexfornuto commented 1 year ago

~Docker tctl command failure: https://github.com/gravitational/teleport/issues/20637.~ Resolved

capnspacehook commented 1 year ago

Error connecting to leaf OpenSSH node: https://github.com/gravitational/teleport/issues/20703

GavinFrazar commented 1 year ago

App Access and require_session_mfa issue: #20634.

Just want to note that my only remaining unchecked task is to use require_session_mfa: hardware_key_touch with app access, which also does not work (obviously)

codingllama commented 1 year ago

App Access and require_session_mfa issue: #20634.

Just want to note that my only remaining unchecked task is to use require_session_mfa: hardware_key_touch with app access, which also does not work (obviously)

Isn't hardware_key_touch functionally equivalent to no session MFA, due to the checks being client-side? Maybe chat with @Joerger to figure out if it's actually supposed to work.

Joerger commented 1 year ago

Just want to note that my only remaining unchecked task is to use require_session_mfa: hardware_key_touch with app access, which also does not work (obviously)

Isn't hardware_key_touch functionally equivalent to no session MFA, due to the checks being client-side? Maybe chat with @Joerger to figure out if it's actually supposed to work.

Yes, hardware_key_touch does actually work in v12, but hardware_key does not as it is functionally equivalent to require_session_mfa: yes. I've tested it so I'll check it off on the test plan.

Edit: I was wrong on this and the test I performed was inadequate (tsh proxy app does prompt for tap, but using the connection fails due to the app session using a different key on the server). This test should have been removed before as this lack of support was already discovered and documented.

GavinFrazar commented 1 year ago

tsh proxy aws --endpoint-url not working in alpha.1 & alpha.2: https://github.com/gravitational/teleport/issues/20798

I think this broke when I did some refactoring work in app access.

GavinFrazar commented 1 year ago

tsh db connect fails when PIV is enabled (not in all configurations): https://github.com/gravitational/teleport/issues/20799

I didn't notice this in my first pass through the test plan because I didn't trip on one of the configurations that has the issue.

fspmarshall commented 1 year ago

DynamoDB

Direct Dial Scaling

Direct Dial Soak

$ tsh bench --duration=30m root@ip-172-31-8-224-us-west-2-compute-internal ls

* Requests originated: 17999
* Requests failed: 0

Histogram

Percentile Response Duration
---------- -----------------
25         156 ms
50         165 ms
75         178 ms
90         188 ms
95         194 ms
99         219 ms
100        2767 ms

$ tsh bench --interactive --duration=30m root@ip-172-31-8-224-us-west-2-compute-internal ps aux

* Requests originated: 17999
* Requests failed: 0

Histogram

Percentile Response Duration
---------- -----------------
25         164 ms
50         174 ms
75         186 ms
90         194 ms
95         201 ms
99         223 ms
100        1677 ms

Tunnel Scaling

Tunnel Soak

$ tsh bench --duration=30m root@ip-172-31-8-224-us-west-2-compute-internal ls

* Requests originated: 17999
* Requests failed: 0

Histogram

Percentile Response Duration
---------- -----------------
25         176 ms
50         183 ms
75         192 ms
90         204 ms
95         212 ms
99         250 ms
100        2229 ms

$ tsh bench --interactive --duration=30m root@ip-172-31-8-224-us-west-2-compute-internal ps aux

* Requests originated: 17998
* Requests failed: 0

Histogram

Percentile Response Duration
---------- -----------------
25         184 ms
50         191 ms
75         201 ms
90         213 ms
95         220 ms
99         260 ms
100        2805 ms

fspmarshall commented 1 year ago

Note about ssh agent forwarding and ssh file copying RBAC tests: The RBAC section of the testplan mentions that we expect access denied to show up in the audit log for all items, but ssh agent forwarding and ssh file copying do not generate access denied events. I checked the code for these checks, and it appears that they aren't intended to emit events currently, so this doesn't seem to be a regression.

I've marked these sections as complete in the testplan because teleport seems to be working as intended, but it may be worth considering adding access denied events for these items.

alexfornuto commented 1 year ago

Verify Teleport versions throughout documentation are correct and reflect upcoming release:

https://github.com/gravitational/teleport/pull/20643

hugoShaka commented 1 year ago

teleport-cluster chart v12 breaks when used with etcd backend: https://github.com/gravitational/teleport/issues/20960

tigrato commented 1 year ago

Pod RBAC fails if the Kubernetes Vendor runs with compression enabled: #20980 - PR: #20981

@hugoShaka detected this issue when running a test in the IBM cloud

ibeckermayer commented 1 year ago

Issue and fix here: https://github.com/gravitational/teleport/pull/21009

alexfornuto commented 1 year ago

Verify upcoming releases page is accurate:

This is under Documentation, but we don't have insight into what's being slated for the next release. I've prepped a page in #21283 for data to be added to, but maybe this should be considered part of #21317

gravitational / teleport

Teleport 12 Test Plan #20132

Manual Testing Plan

User accounting @tigrato

Combinations @capnspacehook

Teleport with EKS/GKE @AntonAM

Teleport with multiple Kubernetes clusters @AntonAM

Kubernetes auto-discovery @tigrato

Kubernetes Secret Storage @tigrato

Kubernetes Pod RBAC @tigrato

Teleport with FIPS mode @r0mant

ACME @mdwn

Migrations @r0mant @zmb3

Command Templates

OpenSSH

Teleport

Teleport with SSO Providers @camscale

GitHub External SSO @Tener

tctl sso family of commands @Tener

Teleport Plugins @greedy52

AWS Node Joining @gabrielcorado

Kubernetes Node Joining @gabrielcorado

Cloud Labels @GavinFrazar

Passwordless @codingllama

Device Trust @sfreiberg

Hardware Key Support @Joerger

Server Access @Joerger

Other @GavinFrazar

Performance @rosstimothy @fspmarshall

Soak Test @rosstimothy @fspmarshall

Concurrent Session Test

Robustness @rosstimothy @fspmarshall

Teleport with Cloud Providers @hugoShaka

AWS @hugoShaka

GCP @hugoShaka

IBM @hugoShaka

Application Access @mdwn

Database Access @smallinsky

TLS Routing @smallinsky

Desktop Access @ibeckermayer

Binaries compatibility @tobiaszheller

Machine ID @timothyb89

SSH

DB Access

Host users creation @lxea

CA rotations @espadolini

EC2 Discovery @lxea

Documentation @ptgott @alexfornuto

Resources

20384 issue with PIV yubikey integration

etcd Load Testing

Agent Mesh

10k Tunnel Nodes

10k Direct Dial Nodes

500 Trusted Cluster

Soak Test

Proxy Peering

10k Tunnel Nodes

10k Direct Dial Nodes

500 Trusted Cluster

Soak Test

DynamoDB

Direct Dial Scaling

Direct Dial Soak

Tunnel Scaling

Tunnel Soak

`tctl sso` family of commands @Tener