Skip to main content

TemplateBuilder and Assembly Upload Services with ADFS

Using either of the templating services (i.e. AssemblyTemplateUploadWebService.asmx and CompoundTemplateWebService.asmx) with ADFS authentication is quite straight forward, if we use the Basic Authenticator. This one exposes a Basic authentication scheme, while communicating with the ADFS server in the background. Once a user is successfully authenticated, it creates a Thread and HttpContext security contexts, so that the following modules in the .NET request processing pipeline execute in the new security context.

As such, our client can define a Basic auth security using HTTPS transport and it will be able to connect to the service. This is the same mechanism the Content Porter application is using (i.e. Basic auth).

App.config

The .NET Console application I use as test client uses generated service proxy classes. The configuration presented below defines the endpoint to connect to and a simple HTTPS Basic auth transport.

  <system.serviceModel>
    <bindings>
      <basicHttpBinding>
        <binding name="MyBinding">
          <security mode="Transport">
            <transport clientCredentialType="Basic" />
          </security>
        </binding>
      </basicHttpBinding>
    </bindings>

    <client>
      <endpoint address="https://web85.playground/templating/CompoundTemplateWebService.asmx"
        binding="basicHttpBinding" bindingConfiguration="MyBinding"
        contract="MyTemplatingService.CompoundTemplateWebServiceSoap"
        name="CompoundTemplateWebService" />

      <endpoint address="https://web85.playground/templating/AssemblyTemplateUploadWebService.asmx"
        binding="basicHttpBinding" bindingConfiguration="MyBinding"
        contract="MyUploadService.AssemblyTemplateUploadWebServiceSoap"
        name="AssemblyTemplateUploadWebServiceSoap" />
    </client>
  </system.serviceModel>

Client Code

The example below connects to the CompoundTemplatingWebService and requests a particular item.

public Example1()
{
    using (var client = new CompoundTemplateWebServiceSoapClient("CompoundTemplateWebService"))
    {
        client.ClientCredentials.UserName.UserName = username;
        client.ClientCredentials.UserName.Password = password;

        var item = client.ReadItem("tcm:0-3-1", EnumOpenMode.OpenModeView, 1);
        Console.WriteLine("Item: " + item.OuterXml);

        var publications = client.GetPublications();
        Console.WriteLine("Publications: " + publications.OuterXml);
   }
}

The second example attempts to upload a templating DLL to the AssemblyTemplateUploadWebService:

public Example2()
{
    using (var client = new AssemblyTemplateUploadWebServiceSoapClient("AssemblyTemplateUploadWebServiceSoap"))
    {
        client.ClientCredentials.UserName.UserName = username;
        client.ClientCredentials.UserName.Password = password;

        byte[] dllBytes = File.ReadAllBytes("dll/my-test.dll");

        var result = client.PerformStoreTemplateAssembly(dllBytes, null, "my-test.dll", "tcm:2-9011-2");
        Console.WriteLine("Result: " + result);
    }
}








Comments

Popular posts from this blog

Running sp_updatestats on AWS RDS database

Part of the maintenance tasks that I perform on a MSSQL Content Manager database is to run stored procedure sp_updatestats . exec sp_updatestats However, that is not supported on an AWS RDS instance. The error message below indicates that only the sa  account can perform this: Msg 15247 , Level 16 , State 1 , Procedure sp_updatestats, Line 15 [Batch Start Line 0 ] User does not have permission to perform this action. Instead there are several posts that suggest using UPDATE STATISTICS instead: https://dba.stackexchange.com/questions/145982/sp-updatestats-vs-update-statistics I stumbled upon the following post from 2008 (!!!), https://social.msdn.microsoft.com/Forums/sqlserver/en-US/186e3db0-fe37-4c31-b017-8e7c24d19697/spupdatestats-fails-to-run-with-permission-error-under-dbopriveleged-user , which describes a way to wrap the call to sp_updatestats and execute it under a different user: create procedure dbo.sp_updstats with execute as 'dbo' as

I Have Gone Dark

Maybe it's the Holidays, but my mood has gone pretty dark. That is, regarding the look and feel of my computer and Tridion CME, of course. What I did was to dim the lights on the operating system, so I installed Placebo themes for Windows 7 . I went for the Ashtray look -- great name :) My VM looks now like this: But, once you change the theme on Windows, you should 'match' the theme of your applications. Some skin easily, some not. The Office suite has an in-built scheme, which can be set to Black , but it doesn't actually dim the ribbon tool bars -- it looks quite weird. Yahoo Messenger is skinnable, but you can't change the big white panels where you actually 'chat'. Skype is not skinnable at all. For Chrome, there are plenty of grey themes. Now i'm using Pro Grey . But then I got into changing the theme of websites. While very few offer skinnable interfaces (as GMail does), I had to find a way to darken the websites... Enter Stylish -- a pl

REL Standard Tag Library

The RSTL is a library of REL tags providing standard functionality such as iterating collections, conditionals, imports, assignments, XML XSLT transformations, formatting dates, etc. RSTL distributable is available on my Google Code page under  REL Standard Tag Library . Always use the latest JAR . This post describes each RSTL tag in the library explaining its functionality, attributes and providing examples. For understanding the way expressions are evaluated, please read my post about the  Expression Language used by REL Standard Tag Library . <c:choose> / <c:when> / <c:otherwise> Syntax:     <c:choose>         <c:when test="expr1">             Do something         </c:when>         <c:when test="expr2">             Do something else         </c:when>         <c:otherwise>             Do something otherwise         </c:otherwise>     </c:choose> Att