The documentation and examples for creating a membership provider are good, so there's no need to cover the basics. I did run into a couple of gotcha's.
First, I really didn't need total customization so I simply extended the Framework's SqlMembershipProvider. If you are using SqlServer, this works fine. The strange thing here is that the connection string, _sqlConnectionString in the provider, is private. This being the case I had to override Initialize and get the value for myself before passing the config along to the base class. Not difficult, just a silly repeat of existing code in the base.
My only other issue was with providing a good message to users if my custom provider Create or Delete operations gave an exception. The basic model on Create is to trap significant issues and log the specific problem while returning null as the MembershipUser and setting the
MembershipCreateStatus to some error type. In this case, the only applicable status is 'ProviderError' which causes a generic message to be displayed to the user. Logging isn't really helpful in this case, so I wrote the real message to a Session variable on the current HttpContext. OnCreateError, i set the error message to this session value.
Otherwise, all I really did was move my code from the OnUserCreated method into the Create method of my new provider. Wired this provider up instead of the other one, and viola!
Hats off to MS on this strategy implementation.
Posts
1 comment:
I created a new assembly with a class that inherits from System.Web.Security.SqlMembershipProvider in the 2.0 version of the framework. I changed the "membership" section of web.config --
<membership defaultProvider="MySqlProvider"><providers><clear /><add.../></providers></membership>
This all then occurred in my site, outside of CS. The issue here was to login to a site outside of CS that would drop a cookie that CS would recognize, and which would allow users to be created on one and recognized at the other.
Post a Comment