git-ecosystem / git-ecosystem/git-credential-manager
Bitbucket user consent shown as Sourcetree
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 9.3k
- Forks
- 2.9k
- Avg merge
- 7d 1h
- Merged PRs (30d)
- 14
Description
When logging in into a Bitbucket Cloud account for the first time OAuth consent is requested for "Sourcetree for Windows". This is counterintuitive for users using for example Git For Windows as they are clearly not using Atlassian Sourcetree. Likewise you have to remember that if you want to revoke app authorization on Bitbucket cloud for your account. This is also problematic from a security standpoint as it educates user to not check what apps they are consenting to and proceed anyways.
This is due to CloudConstants.cs. The code already contains an open todo comment to change this client id and secret as soon as it is approved.
As a user of Git Credential Manager and Git For Windows I expect a consent prompt for the respective GIT backend (e.g. Git For Windows) or at least for Git Credential Manager
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with src/shared/Atlassian.Bitbucket/Cloud/CloudConstants.cs and inspect the existing TODO around the Bitbucket client ID and secret. Confirm the approval status for replacing the Sourcetree credentials and trace where the OAuth consent name is surfaced. Done means Bitbucket consent and authorization management identify Git Credential Manager or the appropriate backend rather than Sourcetree.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, git
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100