Preventing authenticated visitors from browsing system pages

When building an Internet-facing website on the SharePoint 2010 platform, the last thing you want is to have your visitors browse your system pages. To prevent this from happening, SharePoint 2010 has the ViewFormPagesLockdown Feature. But what if your visitors are authenticated? SharePoint 2010 For Internet Sites SharePoint 2010 is

Programmatically granting permissions to claims

Programmatically granting permissions in SharePoint 2007 wasn’t that very complicated. You could grant permissions either to a User or a Group and in order to do that all you needed was a reference to that User/Group. As you might have heard SharePoint 2010 supports claims based identity what

Programmatically determining which Claims Authentication Type has been used to login with Claims Based Authentication

Claims Based Authentication introduced with SharePoint 2010 allows you to login to a SharePoint site using multiple Authentication Providers. In some scenario you might need to determine which Claims Authentication Type has been used to login in order to conditionally show some content. Find out how this can be done

Programmatically converting login name to claim and vice versa

SharePoint 2010 introduced Claims Based Authentication. One of the consequences of this is the fact that in order to use Forms Based Authentication (FBA) you need to configure your Web Application to use Claims instead of Classic Authentication. One of the many changes that you notice while working with claims

A little note to self about custom Membership and Role Providers and SharePoint 2010 Claims

Table of Contents Creating custom Membership and Role Providers Registering custom Membership and Role Providers with SharePoint 2010 Claims Resources Creating custom Membership and Role Providers You can create a custom Membership provider by inheriting from the System.Web.Security.MembershipProvider class. For a custom Role Provider you need to