-
Notifications
You must be signed in to change notification settings - Fork 451
Unauthorized access to Team Server when signing in #111
Comments
@citi-raulfernandez - If everything else works, my guess is that somehow the username or password that you are typing into the Sign In prompt is not correct or was not read correctly. Please confirm that those are exactly the same as the ones you use elsewhere. Note that since this is your company's TFS server, the username should include a domain. Thanks, |
Hi, I tried both (by default it prompts my username with domain), and in all cases it shows the same error message. |
Hi @citi-raulfernandez, After talking with some of our experts here, there may be more going on. Could you describe your server topology. I.e. is there a proxy server? Is there a load balancer? Or any other hoops that the authentication may have to go through? Thanks, |
Let me find out, and I'll come back to you. |
@jpricketMSFT I'm using a VPN and running VS Code inside a VMWare instance. I get the following error message after entering my PAT:
Any ideas on how to resolve this? Thank you. |
@jpricketMSFT Never mind. I figured it out. Apparently I omitted a repo after Correct line should have been: Thank you. |
@skynode - Glad you figured it out! Thanks for posting the solution. |
Closing since there has been no follow-up. |
Hi,
I hope I'm not duplicating any open issue (I read the open ones but they seem slightly different).
I'm using Visual Studio Code 1.9.0 and your latest extension version. We have a git repository in our Microsoft Visual Studio Team Foundation Server 2015 (version 14.102.25423.0).
http://tfs.companyname.net:8080/tfs/projectname/teamname/_git/repositoryName
When I try to signin entering my username (domain/username) and password, I get the 401 error message (when hovering the team icon) See the log below:
I don't have any problem connecting Visual Studio Code with that url, neither accessing it via web.
Any idea what's going on? Any help will be much appreciated.
Thanks
The text was updated successfully, but these errors were encountered: