Claims Based authentication and the PublishingCache

By | 2010-07-06

If you are using Claims Based Authentication on your WebApplication then the Publishing Cache doesn’t work properly.

Have a look into your Developer Dashboard to see what is going on:

The warning and critical error are:

  • 7362 – Warning Publishing Cache
  • 7363 – Critical Publishing Cache

Why is this? Because with Claims Based Authentication the Cache account cannot access the Content Databases.

The solution is to provide your SPWebApplication with two settings (Properties):

  • portalsuperuseraccount
  • portalsuperreaderaccount

If you are lazy, like me, you probably want to automate this into a PowerShell script:

Update 6 juli 2010: This script sets the default managed account as the portalsuperuseraccount and portalsuperreaderaccount. In a production scenario this will work, but it is wiser to use a read only account. Give this account Full Read permission through a Web Application Policy, follow this step-by-step-guide.

6 thoughts on “Claims Based authentication and the PublishingCache

  1. Pingback: The Publishing Cache of SP2010 WebApplications « SharePoint Stef (@vanHooijdonk)

  2. Pingback: The Publishing Cache of SP2010 WebApplications « SharePoint Stef (@vanHooijdonk)

Leave a Reply

Your email address will not be published. Required fields are marked *