by mark
1. September 2010 16:40
I worked all night long and was finally able to get the site up and running with SqlMembershipProvider instead of my home-grown solution.
Why?
- It integrates really well with a lot of available applications written in .Net.
- It is a well-received standard.
- The heavy lifting is handled by the time-tested framework.
- It is just THAT MUCH less code that I have to maintain.
- I really like the administration (roles, specifically) interface that it gives me.
Now that I am starting to expose my WCF services to the world, I wanted to make sure that my login interface uses a standard of some kind. I will probably also upgrade to OpenID or something similar in the very near future as a secondary option to creating an account on my page.
Another cool benefit to my using SqlMembershipProvider is that it gave me a chance to re-evaluate how I was handling accounts in general. Previously, I was requiring lots of information to create an account. I simplified that down to simply take the email, username, password. I may have to integrate a CAPTCHA once people really start using the site to keep things spam free, but am at a stopping point for the login engine as of now.
a29640c2-6f9a-4641-9070-02962f7c3840|0|.0
Tags:
General | code
Subscribe