Any suggestions or experience with moving an existing, non-secure anonymous-access webite into a DotNetNuke portal? I just want to dump the whole site, root and all subsequent folders/pages, into the portal, but not sure if it's possible or how to best do it. I'm looking for DNN to be the security/gatekeeper to the website, so it will not longer be anonymous access. 

Ideally, the portal would be the gateway to the existing site that would operate as is, but under DNN security. Maybe the site would simply run in its own browser, above the portal? The site is basically HTML, but with so many pages and a pretty good existing design that I would rather use it then migrate it all over to HTML/Text modules in DotNetNuke.

Why bother using DNN then? The whole idea of moving to DNN is either for management or security - You would have to set up iframes I guess, but I've never heard of a html file not being accessible once a person knows the url. 

Either way - I've been looking for that elusive *no work required* deal and .. I'm still looking.. oh and for santa claus too because it's that time of the year..

Yep - I'm going to stick my neck out here and say - That's a tough one and I think it won't work. But the idea was good.

Nina Meiers

My suggestion would be either to convert the site to DNN, especially if it's static HTML now anyway, or to use Windows Authentication and secure the site in IIS.  And there's always forms authentication, it's easy enough to set up in ASP.NET 2.0 without having to edit or move content.

Jeff