Open stevenGravy opened 3 years ago
We should improve the error message to help the user switch to a valid cluster (without deleting ~/.tsh
).
Automatically switching to the root cluster might lead to unexpected behavior, like an automated script running tsh ssh user@node backup.sh
. We shouldn't quietly redirect the command to the root cluster node there.
Description
What happened:
A user that logs into a leaf cluster and relogins in later is prevented if the cluster is removed. They get a error on callback The
~/.tsh
folder needs to be removed or possibly altered to reset the user's cluster on login.What you expected to happen:
If a leaf cluster is removed, the user should revert back to the root cluster as their logged in cluster.
Reproduction Steps
As minimally and precisely as possible, describe step-by-step how to reproduce the problem.
Server Details
teleport version
): 6.1.2/etc/os-release
): aws linux 2Client Details
tsh version
): 6.1.1Logs
in the auth server that prevents a user from authenticating completely to start a session.