| By MrBill on Saturday, September 29, 2001 - 02:46 am: Edit |
Website question: How to make a logon page for IIS
Hola, Hombres. I'm working on a very simple website. I'm using IIS 5.0 as the back end. All I want to do is make an HTML or ASP login page with one text box for "username" and one for "password", and a "submit" button. (Instead of the Win2K "Enter Network Password" box.) The username/password info will then be passed to the Win2K ACL via NTFS permissions to see if they have permissions to the virtual directory or not. (I want to use NT group membership instead of some other kind of SQL or Access database to check usernames/passwords).
This would be similar to ClubHombre's login page, but I think he uses Linux...
I think I know how to make a simple logon page (form) as described above, but I don't know how to send this info (username/password) to Win2K for processing (Win2K checks username/password to see if user has NTFS permissions to folder, and can thus be allowed to enter or be declined). I assume this needs some kind of secondary ASP page (with VBScript or WSH???).
This has got to be easy to do, but I can't find how to do it. Anyone? Anyone?
Thanks a million in advance if anyone can help!
MrBillO-
| By Ldvee on Sunday, September 30, 2001 - 12:59 am: Edit |
I'm not sure about this cuz I'm a Linux/php/mysql kind of guy but I think you can put the files where you want authentication in a separate directory and then set sharing on that directory to allow only users specified by using the User Manager in the Admin tools. This should cause the OS to display the usrname/password dialog box. The Win/IIS combo assigns the username IUSR_'servername' to web visitors. Need to disallow that user by disallowing the 'everybody' default. See http://www.authenticationtutorial.com/basic.htm
Alternatively, you could use something like MS Access to build a table of allowable usernames, create an ODBC connection to the db and use VBscript, SQL statements and HTML to build the username input page, database query, and error messages. More work but if you do it you'll know the fundamentals of having a db backend and have much more flexibility.