teleport/.github/ISSUE_TEMPLATE/testplan.md at 8a13de3ef9c40d7ccf520837e5364803b78b9266

mirror of https://github.com/gravitational/teleport synced 2024-10-21 17:53:28 +00:00

Paul Gottschling 491bb0ab7c

* Edit the docs test plan

Add an item to remove version warnings for versions we no longer
support. Currently, we remove these version warnings as we encounter
them. This change makes this task a regular, predictable step when
releasing a new major Teleport version.

* Respond to stevenGravy feedback

2023-06-05 17:40:44 +00:00

64 KiB

Raw Blame History

name	about	title	labels
Test Plan	Manual test plan for Teleport major releases	Teleport X Test Plan	testplan

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.

Adding nodes to a cluster
- Adding Nodes via Valid Static Token
- Adding Nodes via Valid Short-lived Tokens
- Adding Nodes via Invalid Token Fails
- Revoking Node Invitation
Labels
- Static Labels
- Dynamic Labels
Trusted Clusters
- Adding Trusted Cluster Valid Static Token
- Adding Trusted Cluster Valid Short-lived Token
- Adding Trusted Cluster Invalid Token
- Removing Trusted Cluster
- Changing role map of existing Trusted Cluster
RBAC

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

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.
- Adding Users Password Only
- Adding Users OTP
- Adding Users WebAuthn
  - macOS/Linux
  - Windows
- Adding Users via platform authenticator
  - Touch ID
  - Windows Hello
- Managing MFA devices
  - Add an OTP device with tsh mfa add
  - Add a WebAuthn device with tsh mfa add
    - macOS/Linux
    - Windows
  - Add platform authenticator device with tsh mfa add
    - Touch ID
    - Windows Hello
  - List MFA devices with tsh mfa ls
  - Remove an OTP device with tsh mfa rm
  - Remove a WebAuthn device with tsh mfa rm
  - Attempt removing the last MFA device on the user
    - with second_factor: on in auth_service, should fail
    - with second_factor: optional in auth_service, should succeed
- Login Password Only
- Login with MFA
  - Add an OTP, a WebAuthn and a Touch ID/Windows Hello device with tsh mfa add
  - Login via OTP
  - Login via WebAuthn
    - macOS/Linux
    - Windows
  - Login via platform authenticator
    - Touch ID
    - Windows Hello
  - Login via WebAuthn using an U2F/CTAP1 device
- Login OIDC
- Login SAML
- Login GitHub
- Deleting Users
Backends
- Teleport runs with etcd
- Teleport runs with dynamodb
  - AWS integration tests are passing
- Teleport runs with SQLite
- Teleport runs with Firestore
  - GCP integration tests are passing
Session Recording
- Session recording can be disabled
- Sessions can be recorded at the node
  - Sessions in remote clusters are recorded in remote clusters
- Sessions can be recorded at the proxy
  - Sessions on remote clusters are recorded in the local cluster
  - With an OpenSSH server without a Teleport CA signed host certificate:
    - Host key checking enabled rejects connection
    - Host key checking disabled allows connection
Enhanced Session Recording
- disk, command and network events are being logged.
- Recorded events can be enforced by the enhanced_recording role option.
- Enhanced session recording can be enabled on CentOS 7 with kernel 5.8+.
Restricted Session
- Network request are allowed when a policy allow them.
- Network request are blocked when a policy deny them.
Audit Log
- Audit log with dynamodb
  - AWS integration tests are passing
- Audit log with Firestore
  - GCP integration tests are passing
- Failed login attempts are recorded
- Interactive sessions have the correct Server ID
  - server_id is the ID of the node in "session_recording: node" mode
  - server_id is the ID of the node in "session_recording: proxy" mode
  - 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.
- Exec commands are recorded
- scp commands are recorded
- 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
```
Interact with a cluster using tsh

These commands should ideally be tested for recording and non-recording modes as they are implemented in a different ways.
- tsh ssh <regular-node>
- tsh ssh <node-remote-cluster>
- tsh ssh <agentless-node>
- tsh ssh <agentless-node-remote-cluster>
- tsh ssh -A <regular-node>
- tsh ssh -A <node-remote-cluster>
- tsh ssh -A <agentless-node>
- tsh ssh -A <agentless-node-remote-cluster>
- tsh ssh <regular-node> ls
- tsh ssh <node-remote-cluster> ls
- tsh ssh <agentless-node> ls
- tsh ssh <agentless-node-remote-cluster> ls
- tsh join <regular-node>
- tsh join <node-remote-cluster>
- tsh join <agentless-node>
- tsh join <agentless-node-remote-cluster>
- tsh play <regular-node>
- tsh play <node-remote-cluster>
- tsh play <agentless-node>
- tsh play <agentless-node-remote-cluster>
- tsh scp <regular-node>
- tsh scp <node-remote-cluster>
- tsh scp <agentless-node>
- tsh scp <agentless-node-remote-cluster>
- tsh ssh -L <regular-node>
- tsh ssh -L <node-remote-cluster>
- tsh ssh -L <agentless-node>
- tsh ssh -L <agentless-node-remote-cluster>
- tsh ls
- tsh clusters
Interact with a cluster using ssh Make sure to test both recording and regular proxy modes.
- ssh <regular-node>
- ssh <node-remote-cluster>
- ssh <agentless-node>
- ssh <agentless-node-remote-cluster>
- ssh -A <regular-node>
- ssh -A <node-remote-cluster>
- ssh -A <agentless-node>
- ssh -A <agentless-node-remote-cluster>
- ssh <regular-node> ls
- ssh <node-remote-cluster> ls
- ssh <agentless-node> ls
- ssh <agentless-node-remote-cluster> ls
- scp <regular-node>
- scp <node-remote-cluster>
- scp <agentless-node>
- scp <agentless-node-remote-cluster>
- ssh -L <regular-node>
- ssh -L <node-remote-cluster>
- ssh -L <agentless-node>
- ssh -L <agentless-node-remote-cluster>
Verify proxy jump functionality Log into leaf cluster via root, shut down the root proxy and verify proxy jump works.
- tls routing disabled
  - tsh ssh -J <leaf.proxy.example.com:3023>
  - ssh -J <leaf.proxy.example.com:3023>
- tls routing enabled
  - tsh ssh -J <leaf.proxy.example.com:3080>
  - tsh proxy ssh -J <leaf.proxy.example.com:3080>
Interact with a cluster using the Web UI
- Connect to a Teleport node
- Connect to a OpenSSH node
- Connect to a Agentless node
- Check agent forwarding is correct based on role and proxy mode.
tsh CA loading

Create a trusted cluster pair with a node in the leaf cluster. Log into the root cluster.
- load_all_cas on the root auth server is false (default) - tsh ssh leaf.node.example.com results in access denied.
- load_all_cas on the root auth server is true - tsh ssh leaf.node.example.com succeeds.
X11 Forwarding
- 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
- Successfully X11 forward as both root and non-root user
  - tsh ssh -X user@node xeyes
  - tsh ssh -X root@node xeyes
- Test untrusted vs trusted forwarding
  - tsh ssh -Y server01 "echo Hello World | xclip -sel c && xclip -sel c -o" should print "Hello World"
  - tsh ssh -X server01 "echo Hello World | xclip -sel c && xclip -sel c -o" should fail with "BadAccess" X error

User accounting

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

Combinations

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

Connect to a OpenSSH node in a local cluster using OpenSSH.
Connect to a OpenSSH node in a local cluster using Teleport.
Connect to a OpenSSH node in a local cluster using the Web UI.
Connect to an Agentless node in a local cluster using OpenSSH.
Connect to an Agentless node in a local cluster using Teleport.
Connect to an Agentless node in a local cluster using the Web UI.
Connect to a Teleport node in a local cluster using OpenSSH.
Connect to a Teleport node in a local cluster using Teleport.
Connect to a Teleport node in a local cluster using the Web UI.
Connect to a OpenSSH node in a remote cluster using OpenSSH.
Connect to a OpenSSH node in a remote cluster using Teleport.
Connect to a OpenSSH node in a remote cluster using the Web UI.
Connect to an Agentless node in a remote cluster using OpenSSH.
Connect to an Agentless node in a remote cluster using Teleport.
Connect to an Agentless node in a remote cluster using the Web UI.
Connect to a Teleport node in a remote cluster using OpenSSH.
Connect to a Teleport node in a remote cluster using Teleport.
Connect to a Teleport node in a remote cluster using the Web UI.

Teleport with EKS/GKE

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

Teleport with multiple Kubernetes clusters

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.

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

Kubernetes auto-discovery

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

Kubernetes Secret Storage

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

Kubernetes Pod RBAC

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

Teleport with FIPS mode

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

ACME

Teleport can fetch TLS certificate automatically using ACME protocol.

Migrations

Migrate trusted clusters from 2.4.0 to 2.5.0
- Migrate auth server on main cluster, then rest of the servers on main cluster SSH should work for both main and old clusters
- 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

G Suite install instructions work
- G Suite Screenshots are up-to-date
Azure Active Directory (AD) install instructions work
- Azure Active Directory (AD) Screenshots are up-to-date
ActiveDirectory (ADFS) install instructions work
- Active Directory (ADFS) Screenshots are up-to-date
Okta install instructions work
- Okta Screenshots are up-to-date
OneLogin install instructions work
- OneLogin Screenshots are up-to-date
GitLab install instructions work
- GitLab Screenshots are up-to-date
OIDC install instructions work
- OIDC Screenshots are up-to-date
All providers with guides in docs are covered in this test plan
Login Rules work to transform traits from SSO provider
SAML IdP guide instructions work
- SAML IdP screenshots are up to date

GitHub External SSO

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

`tctl sso` family of commands

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:

tctl sso configure github ... creates valid connector definitions
tctl sso configure oidc ... creates valid connector definitions
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.

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

Teleport Plugins

Test receiving a message via Teleport Slackbot
Test receiving a new Jira Ticket via Teleport Jira

AWS Node Joining

Docs

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

Kubernetes Node Joining

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

Azure Node Joining

Docs

Join a Teleport node running in an Azure VM

GCP Node Joining

Join a Teleport node running in a GCP VM.

Cloud Labels

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.
Create an Azure VM with tag foo: bar. Verify that a node running on the instance has label azure/foo=bar.

Passwordless

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.

Diagnostics

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

Device Trust

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
- Add device (tctl devices add)
- Add device and create enrollment token (tctl devices add --enroll)
- List devices (tctl devices ls)
- Remove device using device ID (tctl devices rm)
- Remove device using asset tag (tctl devices rm)
- Create enrollment token using device ID (tctl devices enroll)
- Create enrollment token using asset tag (tctl devices enroll)

Device enrollment

Enroll device on macOS (tsh device enroll)

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

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 ...

Device authorization
- device_trust.mode other than "off" or "" not allowed (OSS)
- device_trust.mode="off" doesn't impede access (Enterprise and OSS)
- device_trust.mode="optional" doesn't impede access, but issues device extensions on login
- device_trust.mode="required" enforces enrolled devices
- 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.
- Role-based authz enforces enrolled devices (device_trust.mode="off" or "optional", role.spec.options.device_trust_mode="required")
- Device authorization works correctly for both require_session_mfa=false and require_session_mfa=true
- Device authorization applies to SSH access (all items above)
- Device authorization applies to Trusted Clusters (root with mode="optional" and leaf with mode="required")
- Device authorization applies to Database access (all items above)
- Device authorization applies to Kubernetes access (all items above)
- Device authorization does not apply to App access (both cluster-wide and role)
- Device authorization does not apply to Windows Desktop access (both cluster-wide and role)
Device audit (see lib/events/codes.go)
- Inventory management actions issue events (success only)
- Device enrollment issues device event (any outcomes)
- Device authorization issues device event (any outcomes)
- Events with UserMetadata contain TrustedDevice data (for certificates with device extensions)
Binary support
- Non-signed and/or non-notarized tsh for macOS gives a sane error message for tsh device enroll attempts.

Hardware Key Support

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

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

tsh login as user with Webauthn login and no hardware key requirement.
Request a role with role.role_options.require_session_mfa: hardware_key - tsh login --request-roles=hardware_key_required

Assuming the role should force automatic re-login with yubikey
tsh ssh
- Requires yubikey to be connected for re-login
- Prompts for per-session MFA

Request a role with role.role_options.require_session_mfa: hardware_key_touch - tsh login --request-roles=hardware_key_touch_required

Assuming the role should force automatic re-login with yubikey
- Prompts for touch if not cached (last touch within 15 seconds)
tsh ssh
- Requires yubikey to be connected for re-login
- Prompts for touch if not cached

tsh logout and tsh login as the user with no hardware key requirement.
Upgrade auth settings to auth_service.authentication.require_session_mfa: hardware_key

Using the existing login session (tsh ls) should force automatic re-login with yubikey
tsh ssh
- Requires yubikey to be connected for re-login
- Prompts for per-session MFA

Upgrade auth settings to auth_service.authentication.require_session_mfa: hardware_key_touch

Using the existing login session (tsh ls) should force automatic re-login with yubikey
- Prompts for touch if not cached
tsh ssh
- Requires yubikey to be connected for re-login
- Prompts for touch if not cached

Other

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

Database Access: tsh proxy db --tunnel

HSM Support

Docs

YubiHSM2 Support (@nklaassen has hardware)
- Make sure docs/links are up to date
- New cluster with YubiHSM2 CA works
- Migrating a software cluster to YubiHSM2 works
- CA rotation works
AWS CloudHSM Support
- Make sure docs/links are up to date
- New cluster with CloudHSM CA works
- Migrating a software cluster to CloudHSM works
- CA rotation works
GCP KMS Support
- Make sure docs/links are up to date
- New cluster with GCP KMS CA works
- Migrating a software cluster to GCP KMS works
- CA rotation works

Moderated session

Using tsh join an SSH session as two moderators (two separate terminals, role requires one moderator).

Ctrl+C in the #1 terminal should disconnect the moderator.
Ctrl+C in the #2 terminal should disconnect the moderator and terminate the session as session has no moderator.

Using tsh join an SSH session as two moderators (two separate terminals, role requires one moderator).

t in any terminal should terminate the session for all participants.

Performance

Scaling Test

Scale up the number of nodes/clusters a few times for each configuration below.

Verify that there are no memory/goroutine/file descriptor leaks
Compare the baseline metrics with the previous release to determine if resource usage has increased
Restart all Auth instances and verify that all nodes/clusters reconnect

Perform reverse tunnel node scaling tests for all backend configurations:

etcd - 10k
DynamoDB - 10k
Firestore - 10k

Perform the following additional scaling tests on DynamoDB:

10k direct dial nodes.
500 trusted clusters.

Soak Test

Run 30 minute soak test directly against direct and tunnel nodes and via label based matching. Tests should be run against a Cloud tenant.

tsh bench ssh --duration=30m user@direct-dial-node ls
tsh bench ssh --duration=30m user@reverse-tunnel-node ls
tsh bench ssh --duration=30m user@foo=bar ls
tsh bench ssh --duration=30m --random user@foo ls

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 web sessions --max=5000 user ls
tsh bench web sessions --max=5000 --web user ls

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

Robustness

Connectivity Issues:

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.
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.
Verify that an open session is not terminated when all Auth instances are restarted.

Teleport with Cloud Providers

AWS

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

GCP

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

IBM

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

Application Access

Run an application within local cluster.
- Verify the debug application debug_app: true works.
- Verify an application can be configured with command line flags.
- Verify an application can be configured from file configuration.
- Verify that applications are available at auto-generated addresses name.rootProxyPublicAddr and well as publicAddr.
Run an application within a trusted cluster.
- Verify that applications are available at auto-generated addresses name.rootProxyPublicAddr.
Verify Audit Records.
- app.session.start and app.session.chunk events are created in the Audit Log.
- app.session.chunk points to a 5 minute session archive with multiple app.session.request events inside.
- tsh play <chunk-id> can fetch and print a session chunk archive.
Verify JWT using verify-jwt.go.
Verify RBAC.
Verify CLI access with tsh apps login.
Verify AWS console access.
- Can log into AWS web console through the web UI.
- Can interact with AWS using tsh commands.
  - tsh aws
  - tsh aws --endpoint-url (this is a hidden flag)
Verify Azure CLI access with tsh apps 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 with tsh apps 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.
Verify dynamic registration.
- Can register a new app using tctl create.
- Can update registered app using tctl create -f.
- Can delete registered app using tctl rm.
Test Applications screen in the web UI (tab is located on left side nav on dashboard):
- Verify that all apps registered are shown
- Verify that clicking on the app icon takes you to another tab
- Verify Add Application links to documentation.

Database Access

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

TLS Routing

Verify that teleport proxy v2 configuration starts only a single listener for proxy service, in contrast with v1 configuration. Given configuration:

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

There should be total of three listeners, with only *:3080 for proxy service. Given the configuration above, 3022 and 3025 will be opened for other services.

lsof -i -P | grep teleport | grep LISTEN
  teleport  ...  TCP *:3022 (LISTEN)
  teleport  ...  TCP *:3025 (LISTEN)
  teleport  ...  TCP *:3080 (LISTEN) # <-- proxy service

In contrast for the same configuration with version v1, there should be additional ports 3023 and 3024.

lsof -i -P | grep teleport | grep LISTEN
  teleport  ...  TCP *:3022 (LISTEN)
  teleport  ...  TCP *:3025 (LISTEN)
  teleport  ...  TCP *:3023 (LISTEN) # <-- extra proxy service port
  teleport  ...  TCP *:3024 (LISTEN) # <-- extra proxy service port
  teleport  ...  TCP *:3080 (LISTEN) # <-- proxy service

Run Teleport Proxy in multiplex mode auth_service.proxy_listener_mode: "multiplex"
- Trusted cluster
  - 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
  ...
```
Database Access
- Verify that tsh db connect works through proxy running in multiplex mode
  - Postgres
  - MySQL
  - MariaDB
  - MongoDB
  - CockroachDB
  - Redis
  - MSSQL
  - Snowflake
  - Elasticsearch.
  - Cassandra/ScyllaDB.
  - Oracle.
- Verify connecting to a database through TLS ALPN SNI local proxy tsh db proxy with a GUI client.
Application Access
- Verify app access through proxy running in multiplex mode
SSH Access
- Connect to a OpenSSH server through a local ssh proxy ssh -o "ForwardAgent yes" -o "ProxyCommand tsh proxy ssh" user@host.example.com
- 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
- Verify tsh ssh access through proxy running in multiplex mode
Kubernetes access:
- Verify kubernetes access through proxy running in multiplex mode
Teleport Proxy single port multiplex mode behind L7 load balancer
- Agent can join through Proxy and maintain reverse tunnel
- tsh login and tctl
- SSH Access: tsh ssh and tsh config
- Database Access: tsh proxy db and tsh db connect
- Application Access: tsh proxy app and tsh aws
- Kubernetes Access: tsh proxy kube

Desktop Access

Direct mode (set listen_addr):
- Can connect to desktop defined in static hosts section.
- Can connect to desktop discovered via LDAP
IoT mode (reverse tunnel through proxy):
- Can connect to desktop defined in static hosts section.
- Can connect to desktop discovered via LDAP
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
- 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.
- Left click and right click register as Windows clicks. (Right click on the desktop should show a Windows menu, not a browser context menu)
- Vertical and horizontal scroll work. Horizontal Scroll Test
Locking
- Verify that placing a user lock terminates an active desktop session.
- Verify that placing a desktop lock terminates an active desktop session.
- Verify that placing a role lock terminates an active desktop session.
Labeling
- 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)
- All desktops have teleport.dev/origin label.
- Dynamic desktops have additional teleport.dev labels for OS, OS Version, DNS hostname.
- Regexp-based host labeling applies across all desktops, regardless of origin.
RBAC
- RBAC denies access to a Windows desktop due to labels
- 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
  - 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
  - The clipboard icon is highlighted in the top bar
  - After allowing clipboard permission, copy text from local workstation, paste into remote desktop
  - After allowing clipboard permission, copy text from remote desktop, paste into local workstation
  - After disallowing clipboard permission, confirm copying text from local workstation and pasting into remote desktop doesn't work
  - 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
  - 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)
  - 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)
  - Attempting to share directory logs a sensible warning in the warning dropdown
- On supported, chromium based browsers (Chrome/Edge)
  - Begin sharing works
    - The shared directory icon in the top right of the screen is highlighted when directory sharing is initiated
    - The shared directory appears as a network drive named "<directory_name> on teleport"
    - The share directory menu option disappears from the menu
  - Navigation
    - The folders of the shared directory are navigable (move up and down the directory tree)
  - CRUD
    - A new text file can be created
    - The text file can be written to (saved)
    - The text file can be read (close it, check that it's saved on the local machine, then open it again on the remote)
    - The text file can be deleted
  - File/Folder movement
    - In to out (make at least one of these from a non-top-level-directory)
      - A file from inside the shared directory can be drag-and-dropped outside the shared directory
      - A folder from inside the shared directory can be drag-and-dropped outside the shared directory (and its contents retained)
      - A file from inside the shared directory can be cut-pasted outside the shared directory
      - A folder from inside the shared directory can be cut-pasted outside the shared directory
      - A file from inside the shared directory can be copy-pasted outside the shared directory
      - 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)
      - A file from outside the shared directory can be drag-and-dropped into the shared directory
      - A folder from outside the shared directory can be drag-and-dropped into the shared directory (and its contents retained)
      - A file from outside the shared directory can be cut-pasted into the shared directory
      - A folder from outside the shared directory can be cut-pasted into the shared directory
      - A file from outside the shared directory can be copy-pasted into the shared directory
      - A folder from outside the shared directory can be copy-pasted into the shared directory
    - Within
      - 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
      - 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
      - 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
      - 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
      - A file from inside the shared directory can be copy-pasted to another folder inside the shared directory
      - A folder from inside the shared directory can be copy-pasted to another folder inside shared directory (and its contents retained)
- RBAC
  - 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)
- Attempting to start a session no keys registered shows an error message
- Attempting to start a session with a webauthn registered pops up the "Verify Your Identity" dialog
  - Hitting "Cancel" shows an error message
  - Hitting "Verify" causes your browser to prompt you for MFA
  - Cancelling that browser MFA prompt shows an error
  - Successful MFA verification allows you to connect
Session Recording
- Verify sessions are not recorded if all of a user's roles disable recording
- Verify sync recording (mode: node-sync or mode: proxy-sync)
- Verify async recording (mode: node or mode: proxy)
- Sessions show up in session recordings UI with desktop icon
- Sessions can be played back, including play/pause functionality
- Sessions playback speed can be toggled while its playing
- Sessions playback speed can be toggled while its paused
- 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.
- 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.
- 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)
- windows.desktop.session.start (TDP00I) emitted on start
- windows.desktop.session.start (TDP00W) emitted when session fails to start (due to RBAC, for example)
- client.disconnect (T3006I) emitted when session is terminated by or fails to start due to lock
- windows.desktop.session.end (TDP01I) emitted on end
- desktop.clipboard.send (TDP02I) emitted for local copy -> remote paste
- desktop.clipboard.receive (TDP03I) emitted for remote copy -> local paste
- desktop.directory.share (TDP04I) emitted when Teleport starts sharing a directory
- desktop.directory.read (TDP05I) emitted when a file is read over the shared directory
- desktop.directory.write (TDP06I) emitted when a file is written to over the shared directory
Warnings/Errors
- Induce the backend to send a TDP Notification of severity warning (1), confirm that a warning is logged in the warning dropdown
- Induce the backend to send a TDP Notification of severity error (2), confirm that session is terminated and error popup is shown
- 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)
  - Confirm that windows desktop sessions can be made on root cluster
  - Confirm that windows desktop sessions can be made on leaf cluster
Non-AD setup
- Installer in GUI mode finishes successfully on instance that is not part of domain
- Installer works correctly invoked from command line
- Non-AD instance can be added to non_ad_hosts section in config file and is visible in UI
- Non-AD can be added as dynamic resource and is visible in UI
- Non-AD instance has label teleport.dev/ad: false
- Connecting to non-AD instance works with Enterprise license
- Connecting to non-AD instance fails with OSS
- Installer in GUI mode successfully uninstalls Authentication Package (logging in is not possible)
- Installer successfully uninstalls Authentication Package (logging in is not possible) when invoked from command line

Binaries compatibility

Verify tsh runs on:
- Windows 10
- MacOS

Machine ID

SSH

With a default Teleport instance configured with a SSH node:

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
Verify you are able to connect to the SSH node using openssh with the generated ssh_config in the destination directory
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
Verify that sending both SIGUSR1 and SIGHUP to a running tbot process causes a renewal and new certificates to be generated
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:

Directly connecting to the auth server
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:

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

Host users creation

Host users creation docs Host users creation RFD

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

CA rotations

Verify the CA rotation functionality itself (by checking in the backend or with tctl get cert_authority)
- standby phase: only active_keys, no additional_trusted_keys
- init phase: active_keys and additional_trusted_keys
- update_clients and update_servers phases: the certs from the init phase are swapped
- standby phase: only the new certs remain in active_keys, nothing in additional_trusted_keys
- rollback phase (second pass, after completing a regular rotation): same content as in the init phase
- 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)
- SSH session in tsh from a previous phase
- SSH session in web UI from a previous phase
- New SSH session with tsh
- New SSH session with web UI
- New SSH session in a child cluster on the same major version
- New SSH session in a child cluster on the previous major version
- New SSH session from a parent cluster
- Application access through a browser
- Application access through curl with tsh apps login
- kubectl get po after tsh kube login
- 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)

Proxy Peering

Proxy Peering docs

Verify that Proxy Peering works for the following protocols:
- SSH
- Kubernetes
- Database
- Windows Desktop
- App Access

EC2 Discovery

EC2 Discovery docs

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

IP Pinning

Add a role with pin_source_ip: true (requires Enterprise) to test IP pinning. Testing will require changing your IP (that Teleport Proxy sees). Docs: IP Pinning

Verify that it works for SSH Access
- You can access tunnel node with tsh ssh on root cluster
- You can access direct access node with tsh ssh on root cluster
- You can access tunnel node from Web UI on root cluster
- You can access direct access node from Web UI on root cluster
- You can access tunnel node with tsh ssh on leaf cluster
- You can access direct access node with tsh ssh on leaf cluster
- You can access tunnel node from Web UI on leaf cluster
- You can access direct access node from Web UI on leaf cluster
- You can download files from nodes in Web UI (small arrows at top left corner)
- If you change your IP you no longer can access nodes.
Verify that it works for Kube Access
- You can access Kubernetes cluster through standalone Kube service on root cluster
- You can access Kubernetes cluster through agent inside Kubernetes on root cluster
- You can access Kubernetes cluster through standalone Kube service on leaf cluster
- You can access Kubernetes cluster through agent inside Kubernetes on leaf cluster
- If you change your IP you no longer can access Kube clusters.
Verify that it works for DB Access
- You can access DB servers on root cluster
- You can access DB servers on leaf cluster
- If you change your IP you no longer can access DB servers.
Verify that it works for App Access
- You can access App service on root cluster
- You can access App service on leaf cluster
- If you change your IP you no longer can access App services.
Verify that it works for Desktop Access
- You can access Desktop service on root cluster
- You can access Desktop service on leaf cluster
- If you change your IP you no longer can access Desktop services.

Documentation

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.

Verify installation instructions are accurate:
- Self-hosted: https://goteleport.com/docs/installation
- Cloud: https://goteleport.com/docs/deploy-a-cluster/teleport-cloud/downloads/?scope=cloud
Verify getting started instructions are accurate:
Verify upcoming releases page is accurate:
- https://goteleport.com/docs/upcoming-releases/
- Only exists for the default docs version.
Verify Teleport versions throughout documentation are correct and reflect upcoming release. Check docs/config.json for this.
Remove version warnings in the docs that mention a version we no longer support except for the last EOL version. E.g., if we no longer support version 10, remove messages saying "You need at least version n to use this feature" for all versions before 10, but keep warnings for version 10.
Verify that all necessary documentation for the release was backported to the release branch:
- Diff between master and release branch and make sure there are no missed PRs
- Ensure that the release branch's documentation content reflects all changes introduced by the release. If not, plan to update the docs ASAP and notify all relevant teams of the delay.
Verify gravitational/docs version configuration:
- Verify latest version in gravitational/docs/config.json
- Verify gravitational/docs/.gitmodules contains latest release
- Ensure that submodule directories in gravitational/docs correspond to those in .gitmodules (remove the directory of the EOL release and create one for the next release)
Verify changelog is up-to-date and complete for the default docs version (CHANGELOG.md). If one release branch has a more complete changelog than others, copy that CHANGELOG.md to our other support release branches.
Verify supported versions table in FAQ (https://goteleport.com/docs/faq/#supported-versions)

Resources

Quick GitHub/SAML/OIDC Setup Tips

64 KiB Raw Blame History

Manual Testing Plan

User accounting

Combinations

Teleport with EKS/GKE

Teleport with multiple Kubernetes clusters

Kubernetes auto-discovery

Kubernetes Secret Storage

Kubernetes Pod RBAC

Teleport with FIPS mode

ACME

Migrations

Command Templates

OpenSSH

Teleport

Teleport with SSO Providers

GitHub External SSO

tctl sso family of commands

Teleport Plugins

AWS Node Joining

Kubernetes Node Joining

Azure Node Joining

GCP Node Joining

Cloud Labels

Passwordless

Device Trust

Hardware Key Support

Server Access

Other

HSM Support

Moderated session

Performance

Scaling Test

Soak Test

Concurrent Session Test

Robustness

Teleport with Cloud Providers

AWS

GCP

IBM

Application Access

Database Access

TLS Routing

Desktop Access

Binaries compatibility

Machine ID

SSH

DB Access

Host users creation

CA rotations

Proxy Peering

EC2 Discovery

IP Pinning

Documentation

Resources

64 KiB

Raw Blame History

`tctl sso` family of commands