In my previous post I explained how to add HTTP Basic authentication to a DD4T REST Service.
If you have done that and your application is consuming content from the REST service, your request should end up in HTTP 403 Not Authorized. This is to be expected, because you have now implemented authentication on the REST service, but the client – the DD4T Rest Provider – does not add any authentication headers to the request by default.
In this blog post we will implement HTTP Basic Authentication on a DD4T REST service. For instructions on how to setup a DD4T RestService follow the instructions described in previous #dd4tdaily articles
DD4T.RestService.WebApi is based on OWIN (Open Web Interface for .NET), a new standardized interface between web servers and web applications. It is meant as a way to break up the tight coupling between ASP.NET and IIS. In this article I will not go in depth on what OWIN is, but it’s essential for this blog post to have a basic understanding on how this works. OWIN allows you to assemble and construct the pipeline of a HTTP Request, by adding so called Middleware to the pipeline. DD4T.RestService.WebApi is a middleware.
Continue reading
In yesterday’s #dd4tdaily post I explained how to setup a default REST service using DD4T 2.0.
Continue reading
With the release of DD4T 2.0 at Tridion Development Summit in Amsterdam in September, an additional way to consume content from Tridion (or SDL Web) was introduced: using a REST Service. In this article you will find a step by step tutorial how to setup this service.
Continue reading
SDL’s documentation contains a list of so-called default claims. These are ambient claims (factoids about the site visitor) which are automatically set by the Ambient Data Framework, even if you don’t have any cartridges installed. You can find the list here: http://docs.sdl.com/LiveContent/content/en-US/SDL%20Tridion%20full%20documentation-v1/GUID-66EDBEF0-FA3D-4B40-A8DB-7A2C7789C903.
Continue reading