RSS Reader, Claims Authentication and Kerberos

In a demo I was helping to set up last week, I had to configure an RSS Reader web part to read an RSS Feed from MySite (The Activity Feed, to be precise). Back in SharePoint 2007, you could not use the OTB RSS Feed Reader web part without running Kerberos, and the same goes for 2010.

However, as it was demo time I also wanted to give us the flexibility of switching to another authentication provider if we got the chance to demo it (eg Live ID) – to do so once it’s initially provisioned requires 4-5 lines of PowerShell script:

If you have not loaded the "SharePoint Powershell Window", you'll need to run 

Add-PSSnapin Microsoft.SharePoint.PowerShell

Then to switch to Claims Auth:

$webApp = Get-SPWebApplication http://mywebapp
$webApp.UseClaimsAuthentication = 1;

And to revert back to Classic mode authentication just change the 1 to a 0 :

$webApp = Get-SPWebApplication http://mywebapp
$webApp.UseClaimsAuthentication = 0;
Too easy!

About Brad Saide

I'm a SharePoint consultant. I'm also slowly going bald, seem to have a permanent spare tyre around my waist and enjoy socialising with friends over a beer or 10. The last 2 may possibly be related. Started working with SharePoint when the first version was in limited beta release (participated in the Technology Adoption Program while at Woolworths) and have been committed to the adoption of the technology as a business enabler ever since.
This entry was posted in Uncategorized. Bookmark the permalink.

2 Responses to RSS Reader, Claims Authentication and Kerberos

  1. James Bean says:

    Unfortunately going from Claims based to Windows based doesn’t work, even after manually repairing the user permissions in the site collections. To go back to Windows Auth I had to detach the database, delete and recreate the webapp as Windows Auth and reattach the database and repair the permissions.

  2. Brad Saide says:

    Hmmm, interesting. The feature is certainly supposed to work, but maybe it’s an SP1 fix? Either way, your approach is a valid workaround until they get the Claims –> Classic authentication change working. Cheers & thanks for sharing!

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s