We are looking at using DNN as a framework on a site which users would get to by logging into one of our primary sites and then clicking a link.  We are tentatively looking at having the primary site pass an authentication token when directing the user to our DNN site, which we would validate using a web service.  We are also looking at possibly not storing the user information in DNN, since all user information is already stored in the primary site.  Is there any documentation on how to rework the login/authentication/membership info so as to accomplish this?  Is this possible with DNN? 

Thanks in advance for any help,

Michael

 

The documentation on this is a bit light, however, I would highly recommend approaching this as an "Authentication Provider" type implementation.

I have done similar processes for 10-15 clients already using web services, and I have a module on snowcovered (External Database Authentication Provider 2.5.0) which does a similar integration using an external SQL Server database. 

You might consider using something like the code for my module as a base and extending that to get your end result.  Overall, with my base code it shouldn't take more than 5-6 hours to implement a complete solution.

If you are looking for consultants to do the work, drop me an e-mail at msellers@iowacomputergurus.com as I mentioned we have built custom auth providers for many clients, some of which are using web services.

---

-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.


Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services