Blog

Back to blog
Setting Up Authenticated Access with TDS

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:

  1. Open the config file. The location and name of this file depends on the version of Visual Studio you are using. You will have to choose the correct file for each version of Visual Studio. The location and name for VS2012 is: C:\Program Files (x86)\Hedgehog Development\Team Development for Sitecore (VS2012)\HedgehogDevelopment.SitecoreProject.VSIP2012.dll.config
  2. Locate the binding: <basicHttpBinding>
  3. Under TdsServiceSoap change:
    1. <security mode=”None”> to <security mode=”TransportCredentialOnly”>
    2. <transport clientCredentialType="None" proxyCredentialType="None" realm="" /> to <transport clientCredentialType="Windows" />
  4. Restart your IDE and test getting items from Sitecore.

How the change will look in screenshots:

Before

After

 

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.

Through a Build Server or MSBuild

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

 

Basic Authentication

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.

Best Of TDS 2015

Share
Tags

4.0 acquisition avtor azure best of tds 2015 back end best practices builds bulgaria code generation charlie turano connection content editor content management code continuous integration delta deploy deployment datasources development feature features feydra guest post front end habitat hedgehog front-end helix how to live chat jenkins jenkins build kliment klimentov launch sitecore mvc rendering miscellaneous mvc nuget package placeholders post deploy step press release preview schackathon sean holmesby security seo rainbow razl sitecore razl 4 razl 4.0 sitecore 9.2 sitecore development sugcon sugcon anz sugcon eu sitecore rocks sxa sitecore roles sync tds tds 5.0 tds 5.6 sitecore user group tds 5.8 tds classic tds classic 5.6 tds classic 5.7 tds classic 5.8 tds classic best practices tds validators technology tfs tom kamin vibert trahan una verhoeven wellness visual studio wffm visual studio online yaml webinar

Related Blog Posts
Sitecore Package Deployer
Creating an automated deployment process around Sitecore update packages can be difficult. The Sitecore Package Deployer is designed to simplify that process by automatically deploying packages from a folder on the Sitecore server.
Setting Visual Studio Online up with TDS
More and more people are starting to use Visual Studio Online. Since TDS 5.0, we supported use with Visual Studio Online. The set up; however, is a bit different with VSO than your local installation.&nbsp;This post will explain how to set up TDS within Visual Studio Online.
Custom TDS Validators
One of the coolest new features of TDS 5 was Validators. Validators allow a developer to have the build automatically check the Sitecore items in the TDS project against specific criteria and generate warnings or errors if the item meets the criteria. This blog post will document the process of setting up your own custom validator.
Enabling HTTPS Support in TDS
A lot of people ask about leveraging a HTTPS connection between their machine and the server. This connection is fully supported, out of the box with TDS. To implement this type of connection you simply need to make sure your certificates are properly managed.