Featured Post

InfoPath, SharePoint and Business Processes – Part 1

Part 1 – The Introduction Recently I did a session at Tech-Ed Africa around using InfoPath as a driver to automate Business Processes and doing this all without coding. As promised in my session, this series of posts will do a step-by-step break down of how to implement a basic InfoPath form, attach...

Read More

Exploring SharePoint 2013 Part 3 : Improvements in the claims infrastructure

Posted by Kevin Coetzee | Posted in 1. SharePoint 2013, 8. General | Posted on 18-12-2012


Continuing from Part 1

SharePoint 2013 also includes the following improvements in claims authentication infrastructure:

  • Easier migration from classic mode to Windows-based claims mode with the new Convert-SPWebApplication Windows PowerShell cmdlet. Migration can be run against each content database and each web application. This is in contrast to SharePoint 2010 Products, in which the migration was run against each web application. For more information, see Migrate from classic-mode to claims-based authentication.
  • Login tokens are now cached in the new Distributed Cache Service. SharePoint 2013 uses a new Distributed Cache Service to cache login tokens. In SharePoint 2010 Products, the login token is stored in the memory of each web front-end server. Each time a user accesses a specific web front-end server, it needs to authenticate. If you use network load balancers in front of your web front-ends, users need to authenticate for each web front-end server that is accessed behind the load balancer, causing possible multiple re-authentications. To avoid re-authentication and its delay, it is recommended to enable and configure load balancer affinity (also known as sticky sessions). By storing the login tokens in the Distributed Cache Service in SharePoint 2013, the configuration of affinity in your load balancing solution is no longer required. There are also scale-out benefits and less memory utilization in the web front-ends because of a dedicated cache service.


  • More logging makes the troubleshooting of authentication issues easier. SharePoint 2013 has much more logging to help you troubleshoot authentication issues. Examples of enhanced logging support are the following:
Separate categorized-claims related logs for each authentication mode
Information about adding and removing FedAuth cookies from the Distributed Cache Service
Information about the reason why a FedAuth cookie could not be used, such as a cookie expiration or a failure to decrypt
Information about where authentication requests are redirected
Information about the failures of user migration in a specific site collection

Comments (1)

[...] SharePoint 2013 Part 3 : Improvements in the claims infrastructureKevin Coetzee summarizes improvements in Claims [...]

Write a comment

Switch to our mobile site