|
IISGate features:
|
> User validation through: |
|
* |
Standard window-based Basic Authentication:
Authentication without cookie, compatible with most browsers, expires with end of user session (closing browser) |
|
* |
Custom web-based Cookie Authentication:
User's browser must accept cookies, compatible with most browsers, the authentication
expires with user session (closing browser) or to a set calendar date |
|
* |
Client IP address:
Grant or deny access directly, without prompt, according to client IP address (good if you have users on your LAN) |
|
* |
Client User-agent:
Grant or deny access directly, without prompt, according to client User-agent |
|
* |
Client Referrer:
Grant or deny access directly, without prompt, according to client Referrer |
|
> Can store users data on custom IISGate INI-style text files or on existing
external database with ODBC connection
|
|
* |
In case of external database,
some features, enjoyable with INI-style
files, will be no availables:
1)Redirection directory.
2)Auto-disabling user after concurrent login event.
3)Users and groups build with standard feature.
|
| > Easy to develop custom
applications with IISGate thanks to INI-style configuration files.
|
|
* |
The 4 configuration files "iisgate_dir.adm",
"iisgate_global.adm", "iisgate_user.adm" and "iisgate_group.adm"
are text files. |
| > Independent of NT users, IISGate uses its own
users database: |
|
* |
Buying additional NT/2000/2003
user licenses is not required, because IISGate users are
independents from operative system. |
|
> Configure access restrictions to directory level (and all subdirectories
automatically): |
|
* |
Authentication prompt is displayed when
a browser
requests a file that resides into a directory (or subdir) that is set
as protected. After authentication user can
navigate free, without others prompts.
The protected directory and all its subdirs, share the same access restriction policy
(protected dir property). |
|
> Personalized user redirection following authentication
(not for external DB): |
|
* |
Powerful feature
allowing to build a single authentication point and personalized user redirection (directory) after
a successful authentication.
Great if you want to have a single web page in your site for all
users authentications.
|
|
> Can set user account expire in x h:min after the first successful login
(not for external DB):
|
|
* |
Powerful feature that
allow to have users with a
one-time login, after that, account expire.
|
|
> Attack protection (client not authenticated after x number of bad login in x
seconds are blocked for x minutes):
|
|
* |
Protect restricted
directory against malicious clients.
If event is verified than client IP is blocked and no authentication
prompts are displayed for set minutes.
|
|
> Can manage concurrent login events.
|
|
* |
If a user account is used by more that one
computer at the same time, you can choose to disabling user account and/or display
warning message to clients for x h:min after event occur.
|
|
> Easy to use, not requires programming, scripting or web development experience.
|
|
> Can administer IISGate from all LAN computers:
|
|
* |
IISGate administration is through
a simply standard
windows program.
|
| > Can organize users in Groups:
|
|
* |
Can grant access to groups and/or single users.
|
| > Log to Windows NT/2000/2003 event log and/or standard text file and/or sending email:
|
|
* |
Every IISGate event is logged on standard text
file and/or
Windows NT/2000/2003 event log service and/or sending email to administrator.
|
|
> Can set user account expire date or disable it manually with a simple selection.
|
System requirements:
Windows NT SP4 or Windows 2000 or Windows XP or Windows 2003, with
Internet Information Server 4/5/6 and Microsoft Data Access Components (MDAC/ADO)
2.0 or grater.
Start protecting your site now, in less than 5
minutes!
Microsoft Windows NT/2000/2003 and Microsoft
Information Server are trademarks of Microsoft Corporation in the United States and/or
other countries |
