-
Bug
-
Resolution: Cannot Reproduce
-
Highest
-
None
-
2.1.8.0
-
None
-
None
-
SourceTree 2.1.8
Git
-
Severity 1 - Critical
After auto-upgrade of SourceTree to 2.4.8, the SourceTree tool lost the ability to authenticate using HTTP when I need to Push/Pull. The issue happens while accessing via terminal window as well
- is cloned from
-
SRCTREEWIN-7727 Lost ablity to authenticate
-
- Closed
-
[SRCTREEWIN-8399] Lost ablity to authenticate
Resolution | New: Cannot Reproduce [ 5 ] | |
Status | Original: Needs Triage [ 10030 ] | New: Closed [ 6 ] |
Workflow | Original: JAC Bug Workflow v3 [ 3453891 ] | New: SRCTREE JAC Bug Workflow [ 3743433 ] |
Workflow | Original: SourceTree Bug Workflow [ 2636203 ] | New: JAC Bug Workflow v3 [ 3453891 ] |
Status | Original: Open [ 1 ] | New: Needs Triage [ 10030 ] |
Assignee | Original: minnsey [ mminns ] |
Description | Original: After auto-upgrade of SourceTree to 2.4.8, the SourceTree tool lost the ability to authenticate using SSH keys when I need to Push/Pull. The issue happens while accessing via terminal window as well | New: After auto-upgrade of SourceTree to 2.4.8, the SourceTree tool lost the ability to authenticate using HTTP when I need to Push/Pull. The issue happens while accessing via terminal window as well |
Description | Original: After auto-upgrade of SourceTree to 2.1.8, the UI tool lost the ability to authenticate using SSH keys when I need to Push. However, if I go to the Terminal window, it asks me for password, and completes the PUSH command. | New: After auto-upgrade of SourceTree to 2.4.8, the SourceTree tool lost the ability to authenticate using SSH keys when I need to Push/Pull. The issue happens while accessing via terminal window as well |
Link |
New:
This issue is cloned from |