How are visitor login accounts typically handled with DotNetNuke? At first glance it appears that they would just be created as CMS users with no access to the administrative roles, and for several reasons that would probably not be a good idea for the implementation I am working on.

1. The site is going to have 150,000 members transferred from the current implementation, and this would make administration of the real CMS users rather cumbersome.
2. I'm a little concerned about the potential for privilege escalation.

I've used Umbraco CMS before, and it maintained a separate MembershipProvider for website visitor logins - I couldn't find any documents on the web describing how this kind of scenario would play out with DotNetNuke - but I'm sure this has to have been done before. Does anyone have any experience with that kind of setup? Are there any kind of issues that I should expect to run into?

Thanks,

Scott

I want to make sure I am understanding correctly - you are advocating having all 100,000+ visitor logins as DotNetNuke users with a security role assigned?