401 Unathorized when trying to connect to on-premises TFS2015 Update 2 (SSL) #59
Comments
|
Hi Amanda. Thanks for trying out the extension! Unfortunately, as you (and some other folks) have found out, there are some issues with being able to connect to Team Foundation servers. The extension connects to Team Services and Team Foundation servers using the vsts-node-api package (which is a different mechanism than what git.exe uses). An issue was reported around load balancers (#55) and you've run into an issue with SSL (there's another at #54). I added the NTLM support relatively recently to the vsts-node-api so we had some basic support for TFS. After doing some debugging, I do see some failures when accessing Team Foundation servers over SSL. Presumably changes to the NTLM handler will need to be made but I don't know what exactly (thinking out loud... perhaps the extension could make use of the CoreCLR in the future as it has much better support for NTLM authentication). Anyway, it's going to require more investigation and digging but I don't have an ETA on when that will occur. That said, I'll certainly add it to our backlog. As you've noticed, connecting over HTTP does work but I'd guess that isn't a workaround for you. I wish I had a better answer at this point. Thanks again for letting us know. |
|
I've also hit this issue as I'm trying to move our TFS server to HTTPS (which is now the suggested configuration). Any updates on this issue? I've set the logging to verbose and I found this: |
|
Hi everyone would like to report the same issue. `2017-05-04T08:03:19.119Z - info: [06224] *** FOLDER: c:\Source\IoT.nxt_Git\IoT.nxt.Workflow\Designer *** Any updates would be appreciated. I like using VSCode environment and using this extension effectively would make life even greater P |
|
Hi @xxGizmoCodexx. It's an issue that I need to investigate and plan on doing it soon. Are you using TFS 2015 (like this thread is about) or 2017 (like #65)? Thanks! |
|
Thanks, @jeffyoung. Good to hear that this matter is being looked into. We are indeed using TFS 2015 |
|
Hi @jeffyoung , is this still in your radar to fix ?do you have approx ETA on it ? |
|
Absolutely. Unfortunately, no, I don't have an ETA. I believe I'll have to investigate the issue in the vsts-node-api package (as the extension depends on that). I sense that the 'fix' isn't going to be a simple "one-liner" but I do expect to start investigating soon (and, yeah, I wish I could be more specific). |
|
I have, in the meantime, reverted to using the method of including '#TFSTaskNumber' in my git commits to link certain code changes to TFS work tasks eg |
|
I have this issue as well. Multiple attempts to do |
|
Same thing here: |
|
I just released version 1.119.0 that should (help to) resolve this issue. I'd be very interested if folks try it out and let me know! |
|
Same issue for me. |
|
Authentication works now, however I'm getting this: |
|
Thanks @jeffyoung for fixing authentication. Authentication works for me but i had to give this in user settings, without this i would not able to connect. "team.remoteUrl": "https://tfs.xyzcom/tfs/defaultcollection", Also , when i edit file, it does not check out the file. why do i see that source control as GIT ? |
|
Hi @markusmauch. Could you provide the rest of the log file (as an attachment, perhaps)? If you're using TFVC, there are a few other calls being made earlier that should log more helpful information. Hi @Yaash19. If you have |
|
Hi @jeffyoung Thanks for quick response. This is what i see when i try to change source control ( i see no option to select TFVC)
Here is my log |
|
Thanks for the log @Yaash19. However, here's what I see:
That tells me that |
|
without team.remoteurl and team.project, i see below error. I do have setup for local workspaces.
My log |
|
Thanks @Yaash19. Can you send a screenshot for your workspace (instructions here)? I'm investigating an issue where a user can get the TF30063 error but that occurs on the second call to workfold (not the first, like yours). In the cases I've seen where you get it with the first call, it's been due to a Server workspace (not Local). |
|
here is my screenshot
Also here my log |
|
I‘m using the latest version 1.119.0 for visual studio team services, but when I trying to use TFVC to connect TFS, Multiple attempts to do Team: Signin end up locking my account. debug: [10188] Error: Failed Request: Unauthorized(401) - https://tfs***/tfs/defaultcollection/_apis/tfvc/branches |
|
Hi @Yaash19. It's odd that the error occurs during the first call to 'workfold' with a Local workspace. To gather more information, would you be willing to do either of the following?
|
|
Hi everybody, I get the same problem of the rest. I have my PC and TFS in the same domain. I can call the _apis in my browser without problems. Microsoft Visual Studio Team Foundation Server Best Regards |
|
Maybe the problem is having more than one folder mapping in the workspace? I'm experiencing the issue since I've set up something like this. |
|
I'm getting a similar error, with or without proxy settings. I only have one folder mapping.
Regards, |
|
I'm still facing the same 'unauthorized' issue even though I have correctly set the tfs location and I'm using a local workspace. What's the status on this issue? |
|
I had exactly the same problem.
|
I have no idea why this works, but it also worked for me! Thank you so much for sharing. |
|
@jeffyoung I hope this helps in troubleshooting: Proxy authentication can be done either by How do I know NTLM works? I use cURL utility reguarly, which by default uses the Negotiate auth scheme, but once I forced it to the NTLM, it worked, so same for VSCode:
You can try other options and see what works for you: |
I have been unable to login using this extension to an on-premises TFS2015 (Update 2) server. Below are the logs:
2016-11-02T19:09:03.664Z - info: [11044] Login: Username and Password provided as authentication.
2016-11-02T19:09:03.838Z - debug: [11044] Parsing values from repositoryInfo as string url
2016-11-02T19:09:03.838Z - debug: [11044] Polling interval value (minutes): 5
2016-11-02T19:09:03.838Z - info: [11044] *** FOLDER: c:\Users\username\Source\Repos\GIT Test ***
2016-11-02T19:09:03.838Z - debug: [11044] No account-specific pinned query or global pinned query found. Using default.
2016-11-02T19:09:03.838Z - debug: [11044] No account-specific token or global token found.
2016-11-02T19:09:03.893Z - debug: [11044] Started ApplicationInsights telemetry
2016-11-02T19:09:03.893Z - info: [11044] Getting repository information (vsts/info) with repositoryClient
2016-11-02T19:09:03.893Z - debug: [11044] RemoteUrl = https://test-tfs.something.com/tfs/Test/_git/GIT%20test
2016-11-02T19:09:03.920Z - error: [11044] Failed (vsts/info) call with repositoryClient: Unauthorized. Check your authentication credentials and try again.
2016-11-02T19:09:03.920Z - debug: [11044] Failed Request: Unauthorized(401) - https://test-tfs.something.com/tfs/Test/_git/GIT%20test/vsts/info
I have setup a TFS server on my local machine (doesn't use SSL) and I am able to login to that without issue.
I am able to clone the origin/remote repository without issue (which uses my credentials), but this extension will not login to the remote TFS server. I am using NTLM authentication.
I am using VSCode 1.6.1 and version 1.108.0 of this extension.
Any ideas?
The text was updated successfully, but these errors were encountered: