mojoPortal uses a custom MembershipProvider named mojoMembershipProvider. It talks to business objects which in turn talk to the db. This way I can support 5 dbs with one provider.

I don't know how hard it would be for you to plug in the standard asp.net membership provider. I suppose if you do it by creating the aspnet membership tables and procs in the same db. Though much of the mojjoportal code uses our SiteUser object which lives in our own mp_Users table. Perhaps a simple solution would be to add some triggers to the aspnet tables to keep the mojo table in sync.

Also mojoportal has a custom profile feature that is way more advanced than the asp.net one.

I think you would be much better off using mojoportal as is than trying to cobble in the standard asp.net providers. Maybe you have a good reason for that requirement but its not what I would do.

Hope it helps,

Joe