Hello Joe and community,

Upon digging deep into the mojoPortal code it seems that a hybrid system is being used to manage mojo's users.
Half of mojoPortal uses ASP.Net Membership Controls and the other half uses the entirly custom built business object SiteUser.

More Detailed Expalanation
MojoPortal uses ASP.Net Membership Controls (i.e. asp:CreateUserWizard, asp:ChangePassword, asp:PasswordRecovery, asp:Login) for registration, changing passwords, recoverying passwords and and logging in.

But, for everything else, MojoPortal uses a business object called SiteUser, (which doesn't inherit from MembershipUser) which allows access to database fields such as: userGUID, AIM, Occupation and Signature. Fields like these don't directly relate to authentication.

Beyond the major difference between the two, namely that SiteUser gives access to additional DB fields.

There are other differences:
* Programmatically, it doesn't seem possible to reset or change a password with SiteUser and ensure that future login's will work as expected. MembershipUser does have the ability to Reset a password with ResetPassword() method.

* While SiteUser does include a Password property, it just reads the value string from the database, whether it's encrypted or not.

* MembershipUser.UserName returns an email address, rather than the the user name the user chose during registration.

Question: Why doesn't SiteUser inherit from MembershipUser?  Are there advantages to this model?

thanks Joe,
Michael

Hello Joe,

Thanks.

I understand that mojoPortal implements MembershipProvider in the class mojoMembershipProvider.  By choosing to create a custom membership provider you can use ASP.NET Membership controls such as <asp:CreateUserWizard>, <asp:ChangePassword>, <asp:PasswordRecovery>, <asp:Login> and still use your own database/datastore design.

And I also now understand that mojoMembershipProvider sits on top of SiteUser and SiteSettings.

But to re-phrase my question, just as mojoPortal uses a custom membership provider, wouldn't mojoPortal also logically implement a custom MembershipUser too?  (in other words, why doesn't SiteUser inherit from MembershipUser, to then support the additional fields that mojoPortal uses?)

Or are there advantages that I can't see with SiteUser as a stand alone class.

Does my question make sense in light of this article? http://msdn.microsoft.com/en-us/library/ms366730.aspx

thank you,

Michael