All geek questions in one place

Remote TFS users ... SSL + password or VPN?

I am currently tasked with setting up a TFS server for the client. Basically, TFS will be accessible by local (local) users through the internal network ... Easy!

But what about the few remote users that we have? Should they connect via VPN or is it better to make the TFS server public and connect to users via SSL and provide a username and password for TFS?

Do you have any suggestions on how these decisions will be implemented compared to each other?

+3
source share
4 answers

A VPN is the way to go if you need the best TFS experience with TFS 2005 or TFS 2008. Although TFS uses web-based protocols that can go over SSL, there are a few small things that won’t work if you don’t have the proper network access. For example:

  • View build log ( if not working )
  • Team Assembly Access
  • Publish Test Results

. VPN- , TFS , TFS, , - , , .. (, , , , :-)). SSL-, , , , , CodePlex , TFS.

VPN , ( TFS - - ). SSL, , , , , , .

. 17 TFS.

+3

: VPN? VPN? ?

( , VPN, SSL)

+2

, VPN. , VPN - , , , , SSL, ...

+1

TFS , , . - TFS - . SSL TFS. .

+1

Source: https://habr.com/ru/post/1714514/

More articles:


All Articles