cathal wrote
You can encrypt webtraffic between the client and server by adding an SSL cert, but this must be installed on the webserver (IIS).
I am finding that this is not completely correct. If you want to use SSL you can only have one single portal use it as a single IIS website can only have a single certificate, which means you do not have the option of using multiple portals. I have heard of one work-around, which is to create a second, third, etc. IIS website for each portal and install its own SSL certificate but to direct it to the same DotNetNuke application directory, however the problem with this approach is that it was reported that this will cause a difference instance of the application to run for each portal, which comes with performance issues of its own.
I have started another thread seeking answers to this delema, however I have yet to receive a responce that convinces me that DotNetNuke is actually capable of handling SSL like many people seem to have claimed.
If you wish to use certificates to secure the site (such as an SSL cert for encrypted web traffic, or a client server for user authentication), this is someone you set up in IIS, and that is transparent to DotNetNuke.
Again, this is not transparent to DotNetNuke as it will break the ability to provide multiple portals in the same application, which to me is one of the primary purposes of DotNetNuke.
If you have any insight that would correct me on this, I would really love to hear it. I currently have a situation where I need to host a credit card store on multiple portals on the same DNN application; and the idea of having to host a separate web application and instance of dotnetnuke.dll for each portal scares me as the performance of DNN is already somewhat high and has not been publically tested (as far as i have found) in this type of hosting scenario.