What's the best practice or design pattern for user registration ?

Question

We have a big portal that needs user registration to allow them use its services. It's already done in .NET and SOL Server 2005. we are in the phase now of discovering all the problems of the current registration system to build a new robust flexible one that can be extended easily and can be more usable for all services.

Could any help me find best practices and design patterns to help me rebuild this using good architectural practices?

Answer 1

This question is really too open ended to give a good answer to. However, I would recommend using the built-in Membership stuff: http://msdn.microsoft.com/en-us/library/tw292whz%28v=VS.100%29.aspx

Answer 2

you can start with the built-in membership component. You can modify that if you need to by modifying the source code.

Answer 3

I would recommend Rhino.Secuirty http://weblogs.asp.net/arturtrosin/archive/2009/04/02/rhino-tools-rhino-security-guide.aspx.

It takes a while to get used to but once you're there you'll see its beauty.

I guess open ended questions receive open ended answers :).