Updating Distributed Logon Cache Settings on SharePoint Farm

As you may know, the distributed cache service on SharePoint 2013 helps improve the performance of many components such as,

• Authentication
• Newsfeeds
• Security Trimming
• Page load performances and etc...

There are different caches exist under the distributed cache service.

The Login Token Cache, which is named as DistributedLogonTokenCache stores security token issued by a Secure Token Service for use by any web server in the server farm. When any web server receives a request for a resource, can access the security token from the cache in order to authenticate and provide access to the resources.

Handling ETag value on SharePoint REST API Updates

ETag value is a part of the HTTP protocol that allows concurrency control and web cache validation. ETag is a broader topic when considered in general, but the main focus on this article is to discuss about REST API usage within SharePoint. 

ETag value is used whenever we make a POST request to a REST API endpoint. This is handled through the IF-Match request header. A sample request is displayed below.

Integrating SharePoint to a Universal App

Recently I came through a requirement that I thought worth trying out a Universal App that consumes SharePoint data. I have chosen Windows 8.1 and Windows Phone 8.1 as the minimal platforms and to support upwards. 

Universal apps bring the power of writing one code that work on both phone and desktop/ tablet devices. This can be done easily in order to create an app that consumes SharePoint data.

This is made simple with the support of C# Managed Code Client Side Object Model. What you need to do is to reference the client side assemblies along with the run-time assemblies. 

SharePoint Workflow REST Call Failure

SharePoint Workflow Manager workflows allows creating workflows that communicate with the SharePoint objects through the REST API calls. End of the day a REST API is connected through the Client.svc endpoint of a particular site. Somehow there are situations I have experienced Cancellation of workflows due to the failures of REST calls. 

There are instances where when you make too many REST API calls, a 429 HTTP Status Code is returned. I have explained this in one of my previous articles here. That is a carefully handled scenario of the Client.svc.