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

Use hostname / IP in a host URLs by default, instead of GUIDs #1514

Closed
kontsevoy opened this issue Dec 15, 2017 · 2 comments · Fixed by #1521
Closed

Use hostname / IP in a host URLs by default, instead of GUIDs #1514

kontsevoy opened this issue Dec 15, 2017 · 2 comments · Fixed by #1521
Assignees

Comments

@kontsevoy
Copy link
Contributor

Intro

Currently Teleport can open a web-based terminal for any node using the following URL format:

https://proxy.example.com:3080/web/cluster/:cluster_name/node/:node_id/:user

node_id can be one of [node_uuid, hostname, node_ip] basically anything a node can be addressed by.

Current behavior

The web UI generates these URLs using node GUIDs. They aren't intuitive for users who wish to use their own.

Suggestion

Use hostname instead.

@klizhentas
Copy link
Contributor

would be also nice to have a way to get a "shareable link" by clicking on some button/icon alongside the list of teleport servers, just like for google docs.

@kontsevoy
Copy link
Contributor Author

kontsevoy commented Dec 15, 2017

@klizhentas right clicking on any link in any browser gives you "copy URL" menu item. Apps that re-implement this do it because they break conventions and do not have reusable links by default (usually due to rich client-side context). Luckily Teleport UI doesn't have this problem, just like any properly done web app (do you see a "shareable link" button for every Github issue? no, you just rick-click and get it)

Oh, and copy-pasting a URL from a browser URL bar works too, since the 90s :)

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

Successfully merging a pull request may close this issue.

3 participants