I'm just getting started with DNN, and it looks like it'll probably do what I need, but I have a couple of basic questions:

1) While I'm working on the transition, is it possible to have DNN's portal just act as a gatekeeper? Essentially, I'd like to have DNN handle log-in, then forward users to the existing HTML pages. I know this should be simple, but I'm new to the CMS concept, and having a bit of trouble wrapping my head around the terminology, which makes it difficult for me to picture how this should work.

2) I read elsewhere in the forum that DNN doesn't have a setting to stop users from changing passwords. For my need, I actually only have one user account, and everyone uses it (this may change in the future, but not soon). Is anyone aware of a module or other method that would allow me to do this? Perhaps a way to just hide the appropriate control?

I apologize in advance if I've missed this elsewhere in the forum or if it's something I either didn't understand in what I've read, or something I missed in documentation. I'm really just struggling to get my head around the concept, so I can figure out if DNN will do what I need in the long term.

Thanks, all!

-Gerry

Thanks, Peter. The "dirty hack" looks like it will do what I need. Once I get around to that point, I'll be sure to post my experience back to this forum.

As far as the first matter, I don't really need to protect those pages. There's nothing sensitive on them, but we had some folks casually copying our content, and we just want to make it more difficult. I'm okay if security isn't great during the transition. I'm expecting to have a DNN-based stie up and running by late January, so it's not a huge deal.

I'll read up some more on authentication, and see if it makes more sense to me. I can be a bit slow until I catch on to the general principles.

-Gerry