gitpod
gitpod copied to clipboard
Add copyable SSH password field to SSH "Access token" panel
Is your feature request related to a problem? Please describe
It's awkward to dig about the current input if you're just looking for your SSH password, for entry into VSCode for example.
Describe the behaviour you'd like
An additional copyable input below with just the SSH password.
Additional context
I know this a bit of a UX nitpick, but my hope is it wouldn't be too much effort to add in.
Thanks for raising @WilliamIPark !
Related feedback from Discord:
Edit: Ignore this and my following post, bad understanding of both my issue and the issue in this original post, sorry I'm a mess :sweat_smile:
I don't really want to post a whole new issue for it, as I just have a question regarding this specifically so sorry if this isn't the best place but... why is access token even needed? We're using a private and public SSH key now, that typically REPLACES password entry. Why this extra step? It seems superfluous and disruptive to me
@Phxntxm the access token method can be handy for just checking out a workspace for once on something like Android+Termux for example. And it can have other usecases as well :smile:
@Phxntxm the access token method can be handy for just checking out a workspace for once on something like Android+Termux for example. And it can have other usecases as well smile
Sure sure, I probably wasn't clear sorry... I'm not asking "why is access token necessary" I am asking "why is access token necessary when using the new Gitpod extension SSH connection, which uses private and public SSH key pairs."
I have reread the original post, and now realize this has nothing to do specifically with that, and now I feel stupid, and this probably should have been a new issue.... oops, my bad. I came to check out these issues with that thought specifically in mind, so I sort of read this interpreting "ssh" as that specifically, sorry for the confusion... I can post this question in a new issue if that's wanted :sweat_smile:
Haha @Phxntxm, no worries, I can relate 😆