Customize Userid/Password Login on webpage

software development

#1

Does anyone have any examples of how to create a custom login screen that pass userid and password allowing access to password protected directories. I’m using raw HTML and Frontpage 2000.

I’m looking for a nice box with login and password on a home page for access to a members area.

I assume I can just pass the parameters (using a form??)… I haven’t done this before…looking for direction.

Thx in advance.


#2

in your webpanel look under Goodies/htaccess from there you can specify a directory to password protect

[color=#0000CC]jason[/color]


#3

I already have a userid and password set on a directory. (I use the goodies htaccess all the time)
At present, when a user presses a link to a Members only (or password protected) directory they are present with an ugly grey dialog box requesting a userid and password.

My question is, can I build a page which has on it a place to enter a userid and a password and then have something initiate and/or pass these as variables through to htaccess/password process.

I would think that this is done all the time. Just looking for the mechanics and an example on how to do this.


#4

[quote]My question is, can I build a page which has on it a place to enter a userid and a password and then have something initiate and/or pass these as variables through to htaccess/password process.

I would think that this is done all the time. Just looking for the mechanics and an example on
how to do this.[/quote]
You can not do what you want with HTTP Authentication, which is the actual name for what you call the “htaccess/password process”. That method has to do with the web server and the web client only, and has nothing to do with HTML/XML, so there is no opportunity for you to “customize” it unless you make your own web client (browser).

What most sites do instead is a process that involces CGI. The first web page has a form and when the form is submitted, a CGI script or program on the web server reads the username and password, checks a database, and either provides a cookie with a session identifier or token. From then on, the pages are generated by CGI scripts or programs that confirm the session or the token is still valid before spitting out the “protected” content.

There are advantages and disadvantages to both methods, and you may want to consult a book or tutorial on the subject especially if your trying to protect valuable content. Try googling for HTTP authentication or CGI authentication.

:cool: Perl / MySQL / HTML+CSS