Quick Tip: Getting MembershipProvider for SPWebApplication

Company | Articles & Research | Services | Software |

Our Company

All SharePoint Articles

Security

Development

Accounting / Dynamics

AIS / Dynamics GP

Other

Consulting Services

Freeware / Experiments

Applications	WebParts	Security Components
SharePoint Field Diff And Copy Utility * Written In January, 2012 SharePoint Security Scanner * Written In January, 2012 SharePoint Kerberos Buddy * Written In Feburary, 2011 BioPoint: SharePoint Biometric Authentication * Written In September, 2007 SharePoint List Security Migrator * Written In August, 2007 SharePoint Anti-Keylogger™ * Written In April, 2006 S.M.A.R.T SharePoint™ * Written In May, 2006 SharePoint Sentinel™ * Written In June, 2006 SharePoint Scrubber™ * Written In July, 2006 SharePoint Safeguard™ * Written In August, 2006	SecureSilverlight For SharePoint * Written In January, 2010 Simple Rollup WebPart For SharePoint * Written In Novemember, 2009 SimpleChart For SharePoint * Written In December, 2009 SimpleSecurity For SharePoint * Written In June, 2009 CrytoCollaboration (Encryption) * Written In June, 2007 Sample AJAX Rotator WebPart * Written In July, 2007 Sample SharePoint Redirector WebPart * Written In August, 2006 WFE Server Name WebPart * Written In January, 2006	PDF IRM Protector * Written In December, 2010 ADAM Role Provider * Written In February, 2007 Universal Provider Framework * Written In April, 2007

Contact

Quick Tip: Getting MembershipProvider for SPWebApplication

When constructing code leveraging the ASP.NET 2.0 membership model that SharePoint employs, you will in due course want to hydrate a System.Web.Security.MembershipProvider object. If you have written custom membership providers, this abstract class should already be recognizable with since its members are implemented in derived provider subclasses.

Ordinarily, you hydrate a strongly typed reference to a MembershipProvider object by providing an uncomplicated index operation on the Membership.Providers collection, austerely supplying the name of the provider:

PLAIN TEXT

C#:

System.Web.Security.MembershipProvider memProvider = System.Web.Security.Membership.Providers["providername"];

Not very fancy :)

An alternative is viable to this by providing two strongly typed parameters, namely a SPWebApplication and SPUrlZone, to return the strongly typed MembershipProvider. To do this, we can use a comparable approach as above, executing an index on the Membership.Providers collection. However we can automate the retrieval of the provider name using the SPWebApplication.GetIisSettingsWithFallback method consuming the SPUrlZone parameter. Subsequently, the MembershipProvider can be queried:

PLAIN TEXT

C#:

public static MembershipProvider BuildMembershipProvider(SPWebApplication app, SPUrlZone zone)
{
return Membership.Providers[app.GetIisSettingsWithFallback(zone).MembershipProvider];
}

Article Or Research Filed Under SharePoint| SharePoint Development.

2 Comments »

Awesome timing, Adam – I was planning to refactor some code this morning around my own ugly implementation! GetIisSettingsWithFallback will provide a much cleaner way to dynamically find the URL of a specific zone based on the configured authentication mode and membership provider, and I would have completely missed this method without your post.

Comment by Dan Kahler — March 3, 2009 @ 9:30 am
[...] Quick Tip: Getting MembershipProvider for SPWebApplication [...]

Pingback by Links (3/4/2009 « Steve Pietrek - Everything SharePoint) — March 4, 2009 @ 7:30 pm