New to TFS 2010 is the concept of a TFS Domain. You can install a domain controller on a server then install TFS 2010 thus creating a seperate TFS domain. Why would you do this? I've have had several clients with security concerns that this appeals to, especially when you are dealing with seperate companies that are sharing a common code base. Consider the scenario: Company A has a partnership with Company B. They are partners in developing in a common code base, but exist in two seperate domains. The security protocols for the companies forbid creating accounts for each other or making TFS publically exposed even through SSL. They have tried using reverse proxies and cannot make it work or work well. They ftp code back and forth but would like to use TFS as a common code respository and/or explore utilizing work items, reports etc.
Enter the TFS Domain. You can take the server that will be hosting your APP tier and install/configure it as a Domain Controller. Install TFS (either single tier or two tier configuration will work). Establish the needed connections between partner domains and TFS domains such as point-to-point VPN. Establish your domain trusts and enjoy your TFS domain. Of course, its not as easy as 1-2-3 but you get the idea!
Well, I hope that helps if you are debating security concerns around TFS access for different domain, perhaps we can drill down at another time! Take care!
