Skip to content

Relogin and hardware key dialogs deadlock in Connect #48121

Open

Description

Reproduction steps:

  1. Set a short TTL for your user (like 1 minute) and require a hardware key.
  2. Log in.
  3. Start a connection to a kube proxy.
  4. After your cert expires, run a command like kubectl version. You will be prompted to log in again.
  5. Try to log in. The dialog (in my case a passwordless dialog) will freeze on the last step:
relogin.deadlock.mov

The problem happens because both Relogin and AskPIN/Touch events try to acquire the same importantModalSemaphore. Because relogin is still in progress, we can't show the hardware key dialog. This in turn doesn't allow us to complete the login :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    bugteleport-connectIssues related to Teleport Connect.test-plan-problemIssues which have been surfaced by running the manual release test plan

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions