Blog Site in Anonymous Use
Anonymous user cannot enter a blog entry in a SharePoint site if ViewFormPagesLockDown feature is active at site collection level and ViewFormPagesLockDown feature is active if site collection is based on publishing portal. After googling we came accross plenty of resources considering this matter:
- Lockdown Mode in SharePoint 2010
- Anonymous access for blog sites not working in SP2010
- Rich Finn’s Blog
We didn’t want use the solutions suggested in the links above. To disable the ViewFormPagesLockDown “…leaves you wide open from a security perspective…”. To have our blog site in another site collection. Well that’s just not what we want to do to solve this tiny little thing with permissions.
Me and Aapo dug with reflector into ViewFormPagesLockDown feature and found out what the feature receiver does.
The highlighted sections of the feature receiver show what happens to Guest’s permissions at rootweb level when you disable ViewFormPagesLockDown site collection level feature.
So why not just take the solution from where it is and develop a web scoped feature which does the exactly same thing to the blog site but not to all webs in the site collection because that’s not what we want.
Develop a feature receiver as follows:
public class FormPagesLockDownReleaseReceiver : SPFeatureReceiver
public override void FeatureActivated(SPFeatureReceiverProperties
using (var web = (SPWeb)properties.Feature.Parent)
var anonymousState = web.AnonymousState;
// continue only if anonymous use is enabled
if (anonymousState == SPWeb.WebAnonymousState.Disabled)
web.AllowUnsafeUpdates = true;
// break inheritance to set permissions per site
// permission granting from LockDownViewFormPages
var byType = web.RoleDefinitions.GetByType(SPRoleType.Guest);
byType.BasePermissions |= SPBasePermissions.EmptyMask |
byType.BasePermissions |= SPBasePermissions.UseRemoteAPIs;
// reset the anonymous state programmatically
web.AnonymousState = SPWeb.WebAnonymousState.Disabled;
web.AnonymousState = anonymousState;
web.AllowUnsafeUpdates = false;
Resetting the anonymous state is just a thing you would have to do from UI when you toggle permissions. Lockdown Mode in SharePoint 2010: “If anonymous is already setup, you may need to disable\re-enable anonymous on the site.”
Then a web scoped feature that consumes the receiver:
Title="Blog Anonymous Access Staplee"
Description="Enables Anonymous Access to Blog Entries"
You could set the feature hidden to avoid accidental feature activations.
Then a stapling mechanism at site collection level to staple the feature to Blog sites by default.
<?xml version="1.0" encoding="utf-8" ?>
<!--Staple FormPagesLockDownReleaseReceiver to Blog sites -->
Title="Blog Anonymous Enabling Stapler"
Description="Staples Anonymous Access to Created Blog Sites"
<ElementManifest Location="Stapling.xml" />
Voila, you have a mechanism to allow viewing form pages only in blog sites when you activate the stapler feature at site collection level. Of course, if you want, you could even set the needed permissions at list level in the Blog site, I suppose, but that’s not what we’ve done here.
Popularity: 3% [?]