Not able to use TFVC; Getting Forbidden (403) about azure-repos-vscode

[jeffyoung]

I've looked into this issue, understand the problem and am working on the solution. Unfortunately, it isn't one of those "one line" fixes and I don't have a solid ETA at this point.

[jeffyoung]

Thanks for all of the feedback on that private build. I just released 1.116.1 with the fix.

@nishantkagrawal I believe that issue is the same as #175 (basically, you've mapped multiple team projects into a single workspace and the extension looks just at the first one).

@paumayr I'd like to hear more about that issue (including what the experience is) when the checkin fails. If you would, I'd appreciate a new issue for it (so I can keep the investigation all in one spot).

[nickyoung23]

I am also getting the same issue. Same error message trying to perform any TFS operations using Visual Studio Code, performing the same operations in Visual Studio 2017 works fine.

TFS server in this case is 2017 Update 1 and the local workspace is a newly created one.

[joshjohanning]

Same issue. Does this extension only work when Basic Auth is turned on the TFS server?

[jeffyoung]

Hi everyone. Thanks for trying out the TFVC support!

Based on this error message fragment, needs the following permission(s) to perform this action: Edit instance-level information, that's a good indication that the issue is related to TFVC permissions. Based on the log file (thanks for providing it!), the extension was able to connect to another server endpoint to validate the collection Url that was parsed out of the workfold command. So the connection to the server is authenticating fine in this case.

The next thing the extension needs to do is get information about the project collection (including the collection name, id and url) and it's at that point we get this error. Once it gets the project collection information, the extension goes out and gets the team project information (including the team project id, name, description and url). All of this information is needed to make additional calls to the server to get back work items, builds, etc.

I'll need to take some time and figure out which call is failing and why (which permissions are necessary). Failing that, perhaps there's another way to get the same information.

@soccerjoshj07 No, you don't need to enable Basic Auth on the server.

[jvsca]

Same here TFS 2015 U3.

[frodesigns]

Also having this issue on a newly set-up TFS 2015 Update 3.

[jeffyoung]

Hi everyone.

I'm finishing up some changes that should address this issue but would appreciate it if you could give the attached VSIX a try? You need to uninstall 1.116.0 and then side-load this VSIX. After downloading the ZIP file, you'll need to rename it to team-0.116.0.vsix (I had to add the .zip suffix so I could attach it here). Then, after selecting the Extension viewlet, click the ... menu and choose Install from VSIX... and then select that VSIX file.

I'd appreciate any feedback (whether it works, doesn't, etc.). Thanks!

team-0.116.0.vsix.zip

[nishantkagrawal]

The error is now gone. I can see the Collection name in the status bar. But still all the changes are listed in the Source Control window instead of just showing the changes in the current folder.

[paumayr]

Hi @jeffyoung, I tried the vsix you attached and it now works for me. Now, I just can't check in because I need to provide a code reviewer ...

[nickyoung23]

Thanks @jeffyoung, the version you attached works for me. I can check out, edit and check in successfully now.

[nishantkagrawal]

@jeffyoung : Correction, The status bar shows me the incorrect project name. I am connected to multiple projects, it is picking up the first one.

[joshjohanning]

@jeffyoung Does TFS on-premises need to have Basic Auth turned on for this extension to work? I am having troubles logging in.

[jeffyoung]

@soccerjoshj07 No, you don't need to enable Basic Auth on the server.

Can you have a look at the other open auth issues and see if any of those apply? If so, it'd be great if I could get your logs to have a look (add them to the issue that applies). If not, please open a new issue and supply as much information as you can. Thanks!