Hello everybody,

I am new to DNN and just started playing around with v6.2.  My problem is as follows:

I have a company wide asp.net application (on entity framework) running on our web server using sql 2008 database with the aspnetDB for the classical membership schema.  This application has already all my users and now that I am creating a specific portal for that application I would like to use the same DB on DNN so that my users will not have to register again.

My original thought was to disable registration from the portal as I do have a registration process already built in my aspnet application.  So I only need the users to be able to login in the portal.  Is there a build in process (via admin or host) to change the membership database?

Thanks for your answer I did not try it cause i found a way of working out my problem.

I had an application already running with the users ready in aspnet_membership db called (AspnetDB). I needed dnn to work on its own db but read the users from the AspnetDB that was already working. Ofc I would have to create the users in the dnn user tabels too.

SoI changed the config of dnn to work with a new connection string for membership purposes only, and I manualy inserted a user in dnn user tables to match the old aspnet_membershipDB.  Checking that machine keys and application names / keys where the same it did not work case DNN uses a vw_users to read and check users while logging. That view had an inner join with:

dbo.aspnet_Membership
dbo.aspnet_Users

so I changed that to my

AspnetDB.dbo.aspnet_Membership
AspnetDB.dbo.aspnet_Users

then copied all users to DNN user tables , roles etc and it works like a charm :)