-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Remote tctl execution. #2991
Remote tctl execution. #2991
Conversation
// | ||
// If the "host auth callback" is not returned, user will be prompted to | ||
// trust the proxy server. | ||
func LoadIdentity(idFn string) (*client.Key, ssh.HostKeyCallback, error) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All this code just moved here from tsh.go
so it could be reused.
retest this please |
@fspmarshall added you as a reviewer |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to clarify, this is essentially an Enterprise-Only feature, yeah? Since OSS doesn't support roles for users.
@fspmarshall Technically, nothing prevents OSS users from exporting identity and using tctl remotely with it too, however what tctl will be able to actually do using this exported identity will be limited by whatever the default OSS "admin" role permits, yeah. |
@klizhentas did you have an ETA to release this feat? |
This PR implements #1525 by adding ability to use
tctl
remotely with--auth-server
and--identity
flags.To use it remotely, a user would first need to export identity locally on the auth server using the usual method:
After that, the exported identity file can be used to invoke
tctl
from a remote node:The
--auth-server
flag can be supplied multiple times.Closes #1525.