We start out with the JavaScript Calendar we created in
Weeks 3 & 6 and "convert" it to ASP. The next step then is
to incorporate database capability with the Calendar. To have
"full" database capability we create three additional pages
that allow us to:
an Event. We now have almost "total" control over the Calendar. One major problem with the setup up to this point is the lack of control on who can Add or Edit an Event. The idea is to allow anyone to view the Calendar but allow only a select few to Add or Edit an Event. So when a User goes to the Add or Edit pages a script will check to see if the User has been "Authenticated". If the User has been "Authenticated" he/she will be allow to that page. If the User has not been "Authenticated" he/she will be Redirected to the Login Page. The User's Name & Password will be checked against a database. If the User is "Authenticated" then the User will automatically be Redirected back the page they were originally going to. Once the User has been "Authenticated" for one page they are automatically "Authenticated" for all the pages that require "Authentication". One minor problem with this implementation is that the person is only "Authenticated" for that Session. In the last step we solve this problem by creating a Cookie for that person so that he/she is "Authenticated" beyond the Session. |