A Little Bit of Apache in an IIS World

This article was originally published on 15 Seconds.

Have you ever wished you could easily set up password-protected areas of your Web site without creating system user accounts? What about moving a password-protected Web site from Apache to IIS? This article examines a free product that makes both of these tasks amazingly simple.

IIS shops that have looked enviously at HTTP authentication capabilities, but have no intention of leaving the Microsoft fold, now have an option: IISPassword.

The product is IISPassword from a company called Troxo. IISPassword is a free download from the ISV's Web site — the full product, not just a temporary trial version — and it is also free for commercial use!


We'll leave the task of describing IISPassword to Troxo. Here's a brief description from the Web site:

IIS password protection of files and folders has always been difficult. IISPassword brings the ease and power of Apache's htaccess to Microsoft IIS. No longer is there a need for system user accounts and complex access permissions for maintaining a secure, password protected web site.

IISPassword uses Basic HTTP Authentication for password protecting web sites on IIS, just like htaccess works on Apache. That makes your password protected Apache web site compatible with IIS, and vice versa.

A powerful and intuitive interface makes it possible to password protect a web site in just moments. More advanced settings provide options such as user group management and protection of certain file types.

Download and Installation

To download the software, a user must fill out a form with his name and e-mail address. Troxo then responds with an e-mail message with a link to a download page. The setup file is just under 5 MB, and although its server wasn't lightning fast, it still downloaded fairly quickly.

Running the setup program starts a relatively standard installation process. After the greeting screen you're prompted to accept the license agreement and then asked if you want to do a typical or custom installation. The only two options in the custom are to install to a different location, and whether or not to register the ISAPI filter in the global IIS

settings, so unless you want to change the location, just run the typical version.

>> Configuration

This article was originally published on 15 Seconds.

This article was originally published on Feb 15, 2006
Page 1 of 2

Thanks for your registration, follow us on our social networks to keep up-to-date