Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0membership login limitationsmembership login limitations
Previous
 
Next
New Post
8/8/2006 3:36 PM
 

I'm trying to create a simple module that will ask all visitors to verify that they are over 21 before entering the website. Legally, my client is required to check that all visitors are over 21 and if they try to access the site by bypassing the  age verification page they will not be able to do so.

In order to do this, I have them fill a form where they enter there date of birth, check against today's date and make sure it's 21 or over. Once the user is verified I automatically log them in under one user account that I have set up. This account has permission to see all the pages while the anonymous account (unauthenticated account) has permissions to see only the age verification page.

Is this the right way to go about making an age verification page ? My biggest concern is if it's possible to have possibly hundreds of users log into the site under this one user account ? Or are there limitations as to how many can log in under one account ?

 

 
New Post
8/9/2006 9:31 AM
 

It is a bad idea to use one account, that is why DotNetNuke has built in security in order to group people together for what they can and cannot see. If you had to terminate one account, how would you be able to do so without destroying everyone's login? How would you know who was doing what on your site?

The best solution is to use the authenticated (registered users) combined with the "Require a valid Profile for Registration" option in User accounts|user settings.  Add a required property and you are ready to go.

Note that asking for a birthdate does not prevent curious and stubborn children from trying to get into your site. There simply is no mechanism to prove the information entered is valid and/or real. You could try billing their credit card for some minimal amount, but they will find their way around that one too.

 


Dwayne J. Baldwin
 
New Post
8/9/2006 10:05 AM
 
I would make a skinobject that checks if a age variable is set in the session. If not the skinobject would redirect the page to the verification page.
There is no need to involve the membership system if your users don't have to register in the first place.


Regarding what djbaldwin said about stubborn children. If you live in the USA you could get into trouble for not preventing access hard enough. you would need to verify age with a visa card. (just google on "age verification" and "mySpace" for more info)

I live in europe. I just state on the firstpage that this site is only for adults over 18 and that this site is not suitable for residents of the USA, wich covers my legal responsibility. I can just put an *enter here* link there, no need to verify anything

Edit your Skin.xml and Container.xml files with:
Yannick's SXE
 
New Post
8/11/2006 6:22 AM
 

Dwayne J. Baldwin
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0membership login limitationsmembership login limitations


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out