March 05, 2015 | Charlie Turano
Every now and again TDS users want to use an authenticated connection to the server. A majority of our users use unauthenticated, but we still need to support authenticated connections. Setting up an authenticated connection is simple and only requires a few additions to your TDS .config files. There are two different ways to go about this depending on your build type (local or through a build server/MSBuild).
Through a Local Build
To set up authentication through a local build follow these steps:
C:\Program Files (x86)\Hedgehog Development\Team Development for Sitecore (VS2012)\HedgehogDevelopment.SitecoreProject.VSIP2012.dll.config
<security mode=”None”> to <security mode=”TransportCredentialOnly”>
<transport clientCredentialType="None" proxyCredentialType="None" realm="" />to
<transport clientCredentialType="Windows" />
How the change will look in screenshots:
Note: In order to get this to work locally while the website binding is associated with the loopback address (127.0.0.1), there's an additional requirement and it's related to how the OS processes authentication requests. This requires some registry changes to be done, the details of which can be found on the following Microsoft article (follow Method 1): http://support.microsoft.com/kb/896861.
In summary, all website bindings pointing at localhost need to be included inside a bypass list. Always do a backup of the Windows Registry before doing changes to it.
The steps for setting up authentication through a build server is very similar as through a local build. The only major difference is in the config file location.
Change the same bindings as with a local build, except the config file is located here:
C:\Program Files (x86)\MSBuild\HedgehogDevelopment\SitecoreProject\v9.0\HedgehogDevelopment.SitecoreProject.Tasks.dll.config
We do not support basic authentication connections as they are widely too insecure. If you are looking to set up a basic connection, we recommend rethinking that option.