Skip to content
This repository has been archived by the owner on Jul 15, 2023. It is now read-only.

change credential in cli #363

Open
markoverflow opened this issue Jan 28, 2017 · 5 comments
Open

change credential in cli #363

markoverflow opened this issue Jan 28, 2017 · 5 comments
Labels
enhancement Indicates general improvement or new feature. help-wanted Indicates that an issue is worth addressing but there is insufficient internal resources to do so.

Comments

@markoverflow
Copy link

how can i change my account credential without manually deleting the current credential in User Accounts >> Windows Credentials

@whoisj
Copy link
Contributor

whoisj commented Jan 30, 2017

That's the only user friendly way. Current, the GCM doesn't support multiple users per Uri. It is something on the backlog, but I've not had time to implement it yet.

@whoisj whoisj added the enhancement Indicates general improvement or new feature. label Feb 7, 2017
@DefSol
Copy link

DefSol commented May 18, 2017

@whoisj so when you say GCM doesn't support multiple users per Uri, would that include the following scenario - I have 2 users on GH say foo & bar. User foo access foo org and user bar the bar org. So in order to navigate such complexities in life, currently the only way is to remove the GH credential in Windows Credentials when switching between foo and bar repos. I had hoped this useHttpPath would give the credential scope, but in my testing it does not seem to be the case.

@whoisj
Copy link
Contributor

whoisj commented May 18, 2017

@DefSol todate, only the Bitbucket authority supports multiple users per domain.

I've plans to port it to the other authority types (Github, VSTS, etc.) but have lacked the spare time to do so.

@DefSol
Copy link

DefSol commented May 18, 2017

Hey @whoisj love the speedy reply! First off, I really appreciate the work you are doing for GCM. Secondly is that pattern for the others (GH, VSTS) the sameish from BB authority? I would be keen to help with this if that's possible?

@whoisj
Copy link
Contributor

whoisj commented May 18, 2017

@DefSol absolutely. The Bitbucket contributor added a check to the username field before operating on the credential, they also make the credential key unique by adding the username to it.

Should be fairly straightforward to re-implement across the board. Would love to see a contribution from you. 😄

@whoisj whoisj added the help-wanted Indicates that an issue is worth addressing but there is insufficient internal resources to do so. label Aug 1, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Indicates general improvement or new feature. help-wanted Indicates that an issue is worth addressing but there is insufficient internal resources to do so.
Projects
None yet
Development

No branches or pull requests

3 participants