| Summary: | Username not editable | ||
|---|---|---|---|
| Product: | [Technology] EGit | Reporter: | Ian Bull <irbull> |
| Component: | UI | Assignee: | Project Inbox <egit.ui-inbox> |
| Status: | NEW --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | mkempka, mknauer, remy.suen |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Ian Bull
This can be easily seen by: 1. Go to the Git Repository View 2. Clone a repo 3. Use ssh://foo.com/foo 4. Don't enter any username 5. Hit next It will try to connect, and since it can't it will prompt for a username / password. However, the username will be READONLY. Obviously in this case you could go back to the first page and enter a username, but that's not an option when you just use the clone operation. Is there a reason that JschConfigSessionFactory forces the current user if none is set? Ping... any thoughts on this? Having non-editable user names and assuming that everyone has the same username everywhere is real problem. Or is there something I'm missing? |