[Workbench] [Documentation] Display https url in repositories panel in manage_account page. Update documentation as needed.
- Create/store a private key on the shell node. This is a bad practice.
- Don't use SSH to authenticate to git repos when logged in via webshell.
The infrastructure is in place (pending #6619) to authenticate via https using the arvados API token that is automatically added to your environment at login time. Of course, this only helps when you clone/push
https://git.zzzzz.arvadosapi.com/foo/bar.git -- but doc.arvados.org and Workbench's "Manage Account" page only suggest using the url
- Clone with HTTPS if your ARVADOS_API_TOKEN env var is set (e.g., you're logged in to an Arvados shell VM). This is the best option for shell VMs even if you're logged in with SSH: it means "push" will work next time you log in, even if you log in with Webshell.
- Clone with SSH if you've added your SSH key to Arvados and it's available in your login session (e.g., you're cloning to your workstation).
#1 Updated by Tom Clegg over 6 years ago
- Subject changed from [Workbench] Display https url in repositories panel in manage_account page. Update documentation as needed. to [Workbench] [Documentation] Display https url in repositories panel in manage_account page. Update documentation as needed.
- Description updated (diff)
- Category set to Workbench
- Story points set to 1.0
#7 Updated by Tom Clegg over 6 years ago
Changes look good, thanks.We need to add guidance about how to authenticate when using the
https://urls. I'm on the fence about whether that should block merging db25848.
- Shouldn't block: it "just works" from a shell VM thanks to #6619, so no instructions are needed.
- Should block: if used from your workstation, it will ask for a username/password, which will be mysterious because Arvados has no passwords. At least with the SSH option, a worldly user would guess that they need to provide a public key just like on Github.
Suggest wording for guidance (edits welcome):
"If you are prompted for credentials when using https URLs, provide "none" as your username and your Arvados API token as your password. When you are using an Arvados shell account, credentials are handled automatically."
#9 Updated by Peter Amstutz over 6 years ago
- "If you are prompted for username and password when you try to git clone using this command, it would mean that git config needs to be updated:"
This is a little too passively worded. How about "If you are prompted for username and password when you try to git clone using this command, you may first need to update your git config:"
Everything else looks good.