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

Expand/document remote tctl execution #1525

Closed
klizhentas opened this issue Dec 21, 2017 · 6 comments · Fixed by #2991
Closed

Expand/document remote tctl execution #1525

klizhentas opened this issue Dec 21, 2017 · 6 comments · Fixed by #2991
Assignees
Labels
tctl tctl - Teleport admin tool

Comments

@klizhentas
Copy link
Contributor

Description

Sometimes it makes sense to execute tctl command non locally, e.g see comment.

Tctl by design supports remote auth server execution, however there is no UX flow for this yet.

This issue specifies additional configuration flags and UX flow for those cases.

Auth sign

Auth sign will be extended to generate identity in the format understood by tctl.
Users will have to create a special admin user with defined roles and will be able to issue client certificates for auth server authentication:

tctl auth sign --user=admin --out=identity.pem --format=tctl

The resulting identity.pem is a pair of x509 key and client certificate that could be used to communicate to the auth server.

Connecting to remote auth servers

Later on, users or robots can issue commands remotely:

tctl --auth-servers=https://auth-server-1,https://auth-server-2 --identity=identity.pem get users

--auth-servers flag is added to point to remote auth servers (right now, the list of auth servers is pulled from the config file)

--identity flag is added to point to the client certificate/key pair pem file for authentication.

pem file also contains certificate authority to trust as issued by the auth server, so client can verify the identity of the auth servers it is conecting to

@kontsevoy
Copy link
Contributor

The CLI syntax is TBD

@MattiasGees
Copy link
Contributor

Where can we find the spec on how the format of a tctl file has to looks like?

@kontsevoy
Copy link
Contributor

@MattiasGees sorry I'm not following. what do you mean by "tctl file"?

@kontsevoy
Copy link
Contributor

if you meant "config file" it's the same one teleport daemon uses, i.e. /etc/teleport.yaml which is documented.

@kontsevoy
Copy link
Contributor

@klizhentas can we make the CLI identical between teleport and tctl? Teleport uses:

teleport start --auth-server=10.0.5.5

i.e. it's "server" without "s" and it doesn't require https prefix. I would propose we make both forms acceptable --auth-server and --auth-servers and let both forms take a comma-separated list, but drop "https://" schema

@kontsevoy
Copy link
Contributor

BTW I believe in Teleport you can do start --auth-server=one --auth-server=two

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

Successfully merging a pull request may close this issue.

5 participants