|
IISKeeper. It is nothing personal, Sonny. It is strictly business.
|
|
| Updated |
Apr 6, 2006 16:43:45 | | Author email | anikolaev@3d2f.com | | Author | Nikolaev Alexander Dmitrievich |
|
|
It is not a rare and absolutely normal situation when you want to protect some resource on your web-site and grant access to it on the per-user basis. As a matter of fact, the organization of almost any pay-per-view resource requires this capability. Unfortunately, with IIS you can’t create a protected resource easily. But with IISKeeper you can.
IISKeeper works as an ISAPI filter for IIS and can protect resources with any granularity, whether there is a single file, small folder, or a large folder tree to be protected.
The filter is easily installable (all Windows server OS are supported), you are not even required to restart IIS while working IISKeeper. All you need to do after the installation is to create a user list, then select resource to be protected, and then select which users are allowed to access to that resource. When someone attempts to access the protected resource, he or she would be prompted for the user name and password (there is a choice between the «basic» and «cookie» authentication and additional protection against the password guessing through the per-IP blocking from attacks).
User access is widely configurable; for example, you can restrict the amount of traffic a user can consume or suspend a user temporarily (without deleting that user from list). IISKeeper can protect even HTTPS (secure) resources. All filtering are reflected in the log files.
Author: Nikolaev Alexander Dmitrievich | |
| | Learn more about IISKeeper… |
|
|
