Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Teleport login problem #1611

Closed
klizhentas opened this issue Jan 17, 2018 · 1 comment · Fixed by #1618
Closed

Teleport login problem #1611

klizhentas opened this issue Jan 17, 2018 · 1 comment · Fixed by #1618
Assignees
Labels

Comments

@klizhentas
Copy link
Contributor

What happened:

Tsh login does not work normally with two proxies/auth servers connected to the same SAML/OIDC auth provider.

What you expected to happen:

Credentials will work for both first proxy and second proxy.

How to reproduce it (as minimally and precisely as possible):

Have two proxies/auth servers connected to the same OIDC/SAML provider.
Login to the first proxy with a user
Login to the second proxy with a user

As long as user does second login, tsh ls stops working for both first and second login, always prompting user to relogin.

Environment:

  • Teleport version (use teleport version):
    2.4.0

  • Tsh version (use tsh version):
    2.4.0

  • OS (e.g. from /etc/os-release):
    linux
    Browser environment
    N/A

  • Browser Version (for UI-related issues):

  • Install tools:

  • Others:

Relevant Debug Logs If Applicable

  • tsh --debug
  • teleport --debug
@klizhentas
Copy link
Contributor Author

It picks wrong keys when username is the same, this interface should accept proxy name as a parameter and use the keys from currently logged in proxy.

https://github.com/gravitational/teleport/blob/master/lib/client/keystore.go#L117

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants