Authenticating user identities in ASP applications (1)

Interactive Web applications require more security than sites that provide only static Web pages. Registration and password are the most common means of protecting sensitive information. Because the ASP does not directly provide a way to authenticate the user, the user must perform the logon process so that the application system can save and extract user-related information.
Overview of sample Sites

This paper illustrates the general implementation of registration and password protection in ASP application through a sample site aspsecurity
Process. We keep the user information in a ACCESS97 database on the Web server, and the DSN name is called
Aspsecurity. The unique database table has the following fields: Signon (text, registered username),
Password (text, password), Laston (text, user last accessed time), timedout
(Yes/No, whether the session was terminated by the system due to a timeout).

The system mainly includes the following several pages:

default.htm--redirects the browser to the Signon.asp page.

signon.asp--provides a login system interface.

signedon.asp--the page displayed after the system was successfully logged in.

register.asp--New User Registration page.

The default page default.htm is used only to redirect the browser to the signon.asp login page, which is
Face this META tag implementation:

< META http-equiv= "REFRESH" content= "1; Url=signon.asp ">

The Signedon page is the only protected page for the entire site and must be authenticated for access.