How would somebody go about making sure that password submissions and credit card feilds are secured in DNN, specifically on applications that host multiple portals using different host headers?  I am a little bit concerned by how little information I've been able to find on this.  I've found a few solutions that make is so that all pages are secured, but that will only work on a single host header at a time.

Please somebody tell me if this is or isn't possible with the core product?

Thanks

If you plan to store credit cart information in DNN, i astrongly recommend doing so on a dedicated server. I definitely wouldn't store financial information on an install shared with other portals. If you can't isolate the data I'd recommend using a system such as PayPal where your site never gets the actual credit card number.

---

Qualtiy DotNetNuke modules and custom development; we've been serving the DNN community for over 2 years and have hundreds of satisfied customers. Let us serve you today.

I have my own servers and am setting up a DNN application to host portals that integrate with an on site windows forms application at client sites to handle reservations and account transactions on the web that are replicated to the enterprise solution my clients use on site.

I am not concerned with the data after it has made it too my site, what I am concerned with is that when the user types their credit card information in the submit form, that the information would be trasfered as clear text to my server where it could then get encrypted and saved.  Not being able to support this on multiple portals on the same DNN application seems to me to be a critical flaw in the DNN core architecture. 

Does this would mean that every single site that uses the DNN STORE project with paypal and authorize.net integration is currently not submitting encrypted postbacks to the server?  This sounds like a huge problem, I am hoping that I'm just overlooking something obvious and that somebody will correct me.