We are creating a DNN site and plan to use the forms authentication with the the DNN MembershipProvider functionality. For security purposes, we are needing to have all aspnet tables behind out firewell (not the content tables though). We would like to have a service layer between the DNN site and the aspnet database, but do not plan to modify the underlying functionality of the authenication credentials data store. Since I am a relative novice with DNN, how would I need to modify the DNN source to use the new service and are there any additional steps to do this? Any further references where this has been done before would be appreciated. I can't imagine this is a question that is has never come up. Thanks.

Thanks for the reply Mike.

The DNN site is sitting on external server. The suggestion of poking a hole is exactly what we are trying to avoid per requests from our network team, therefore a service layer is the best practice approach.

I am also looking into creating a customer Member Provider when uses a service layer; so hopefully I can make headway on that. Any further information will be appreciated.

Did you mean "It is best practice to place the APPLICATION server behind the 2nd firewall, while the web server is placed in DMZ." ?

I've never used DNN.

I wonder the effort needed to have DNN in DMZ not speaking with database, but speaking (in wcf?) only with a Service Layer (running on iis behind the firewall),

Is it all possible with DNN without code changes?

Regards