I've been reading articles all afternoon and after all this, I'd like to bounce this idea off of those who have done this before.  We have an LDAP server on which we authenticate for many other web applications.  We already have an application for administering the users and their roles for this server.  Adding and deleting users and roles would be done from this main application.  With this in mind, we will most likely turn off the abiliy to administer users and roles on our implementation of DNN.  All authentication would come real-time from our LDAP server and we would provide a module that would let users edit basic contact information in the LDAP server.  This would mean that we would most likely also turn off the "My Account" functionality on DNN. 

Having said all that, my thought was that all we would have to do is create a new Data Provider that inherits the DotNetNuke.Security.Membership.DataProvider class.  No pre-loading of the User tables, no synchronization between the LDAP server and DotNetNuke, just a simple replacement of the provider.

Is my idea the kind which you would expect from someone on crack or a glue-sniffer?  Or does it have some merit?  Responses from people in the know would be appreciated.  Thanks.