A client has asked me to develop a DNN module for their new site.  This module will have nothing to do with DNN other than being a module...it is a customer support module that ties directly into their existing, non-DNN-related databases.  It will implement user/security outside the realm of DNN.

I normally implement forms authentication in standard ASP.Net apps...what would be the appropriate independent security model for a DNN module (other than using the built-in structure)?  Cookies/Session variables?

Is it possible to have a module with an exposed login component you can drop anywhere within DNN that successfully authenticates and redirects the user to the rest of the module on another page?  Or does that require two modules?

Thanks!

As I said, DNN security is not an option, which is why I'm looking for alternatives. Thanks!

The customer wanted to build a DNN module as part of the new DNN site they are rolling out that does not use the DNN security/membership, but rather it's own internal user management and security (they wanted to use the DNN membership for their internal users only). In a regular website, I would just use Forms Auth and my own custom authentication and user components, but since these are modules, that won't work. However, I may have the customer convinced to use the standard DNN membership services. Fingers crossed...