You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If access workflows are enabled and a user on a mac removes their .tsh directory before issuing a login command similar to tsh login --proxy=proxy.example.com --request-reason=testing --ttl=2 --auth=auth0 without specifying a user with the --user flag, they encounter the following error:
User Message: failed to authenticate with proxy proxy.example.com:3023
Rerunning the same command again does not trigger the error.
This only happens when using access workflow flags (either request-roles or request-reason) AND the .tsh directory is removed. It only happens the first time the user attempts to authenticate that way after removing the directory.
What you expected to happen:
User should be able to log in without having to explicitly set the --user flag the first time after removing the .tsh directory like they can when access workflows are not involved.
How to reproduce it (as minimally and precisely as possible):
run rm -r ~/.tsh on a mac
Issue following command when access workflows are enabled: `tsh login --proxy=proxy.example.com --request-reason=testing --ttl=2 --auth=auth0' (also repeatable with --request-roles and any auth connector)
Observe error and no request token generated even though browser will show a successful Login redirect.
Issue same command again.
Observe request token generated and login successful after approval.
trying the same thing with tsh login --proxy=proxy.example.com --request-reason=testing --ttl=2 --auth=auth0 [email protected] does not trigger the error.
Environment
Teleport version (use teleport version): 4.4 and 5.0
Tsh version (use tsh version): 4.4. and 5.0
OS (e.g. from /etc/os-release): OSX
Relevant Debug Logs If Applicable
Logs from Mac on unsuccessful login:
DEBU [KEYSTORE] Returning SSH certificate "/Users/user/.tsh/keys/proxy.example.com/[email protected]" valid until "2021-01-15 13:14:43 -0500 EST", TLS certificate "/Users/user/.tsh/keys/proxy.example.com/[email protected]" valid until "2021-01-15 18:14:43 +0000 UTC". client/keystore.go:319
DEBU [CLIENT] Client is connecting to auth server on cluster "ip-192-168-1-1-ec2-internal". client/client.go:473
INFO [CLIENT] no host login given. defaulting to user client/api.go:801
INFO [CLIENT] [KEY AGENT] Connected to the system agent: "/private/tmp/com.apple.launchd.ucd29VQBE6/Listeners" client/api.go:2282
ERRO [KEYSTORE] open /Users/user/.tsh/keys/proxy.example.com/user-cert.pub: no such file or directory client/keystore.go:253
Logs from Mac on successful login:
DEBU [KEYSTORE] Returning SSH certificate "/Users/user/.tsh/keys/proxy.example.com/[email protected]" valid until "2021-01-15 13:12:25 -0500 EST", TLS certificate "/Users/user/.tsh/keys/proxy.example.com/[email protected]" valid until "2021-01-15 18:12:25 +0000 UTC". client/keystore.go:319
DEBU [CLIENT] Client is connecting to auth server on cluster "ip-192-168-1-1-ec2-internal". client/client.go:473
INFO [CLIENT] no host login given. defaulting to user client/api.go:801
INFO [CLIENT] [KEY AGENT] Connected to the system agent: "/private/tmp/com.apple.launchd.ucd29VQBE6/Listeners" client/api.go:2282
DEBU [KEYSTORE] Returning SSH certificate "/Users/user/.tsh/keys/proxy.example.com/[email protected]" valid until "2021-01-15 13:12:25 -0500 EST", TLS certificate "/Users/user/.tsh/keys/proxy.example.com/[email protected]" valid until "2021-01-15 18:12:25 +0000 UTC". client/keystore.go:319
INFO [KEYAGENT] Loading key for "[email protected]" client/keyagent.go:147
The text was updated successfully, but these errors were encountered:
Description
What happened:
If access workflows are enabled and a user on a mac removes their .tsh directory before issuing a login command similar to
tsh login --proxy=proxy.example.com --request-reason=testing --ttl=2 --auth=auth0
without specifying a user with the--user
flag, they encounter the following error:User Message: failed to authenticate with proxy proxy.example.com:3023
Rerunning the same command again does not trigger the error.
This only happens when using access workflow flags (either request-roles or request-reason) AND the .tsh directory is removed. It only happens the first time the user attempts to authenticate that way after removing the directory.
What you expected to happen:
User should be able to log in without having to explicitly set the --user flag the first time after removing the .tsh directory like they can when access workflows are not involved.
How to reproduce it (as minimally and precisely as possible):
rm -r ~/.tsh
on a mactrying the same thing with
tsh login --proxy=proxy.example.com --request-reason=testing --ttl=2 --auth=auth0 [email protected]
does not trigger the error.Environment
teleport version
): 4.4 and 5.0tsh version
): 4.4. and 5.0/etc/os-release
): OSXRelevant Debug Logs If Applicable
Logs from Mac on unsuccessful login:
Logs from Mac on successful login:
The text was updated successfully, but these errors were encountered: