Release History
Version 5.0 beta 2 (2003/4/20)
- Bug: If the server is member of a NT Domain, an error message is reported
when initializing an instance of the filter (fixed in beta 3)
- Bug: If several HTTP queries are received while initializing an instance
of the filter an error message may be reported (fixed in beta 3)
- Bug: Various minor interface problems with DAF Configuration Tool (fixed
in beta 3)
- Bug: Domain Administrators are not seen as Local Administrators (fixed in
beta 4)
- Bug: SQL Server Data store: Wrongly reported error: "ODBC:Connected to
database <> instead of <>" (fixed in beta 5)
- Bug: If work files "dbiis<SiteID>_readlockcnt.mem" are corrupted the
filter cannot recover even after restarting (fixed in beta 5)
- Bug: An XML User Database may be corrupted while updating a user visit
date and hit count (fixed in beta 5)
- Bug: Passwords of mapped NT accounts are corrupted and will generate
log-in failures (fixed in beta 5)
- Bug: Mapped NT accounts which are domain users aren't handled correctly
and will generate log-in failures (fixed in beta 5)
- Bug: Log cache events does not log all events (fixed in beta 6)
- Bug: [Security Handler settings/UserID & Session/Browser Login &
Password/On successful logon, save in cookies] does not work. Cookies are not
set (fixed in beta 6)
- Bug: "Always use a SSL connection" does not work with Basic authentication
(fixed in beta 6)
- Bug:Web site "DAFEngine" is incorrectly created by the installation
program (fixed in beta 6)
- Bug: Message sent to the NT event queue are no longer
displayed with an error (fixed in beta 7)
- Bug: Memory leak in LOGCLIENT.EXE (fixed in beta 7) (build
5601)
- Bug: (Beta build only) Site license is Unregistered after
updating the Security Handler settings (fixed in beta 7)
- Bug: Access to a DAFAUTH.INI protected resource is denied
to forwarded NT Accounts (fixed in beta 7)
- Bug: IP Filter added by another IP Filter are not active.
Security Handler must be restarted (Fixed in beta 7)
- Bug: Administrators email addresses are not saved
correctly (Fixed in beta 7)
- Bug: Installation fails if no global filter exist in the
IIS configuration (Fixed in beta 7)
- Bug: ODBC: one permsistent connection is used even none is
requested (Fixed in beta 7)
- Bug: ODBC: when User DB settings are updated, the
LocalCopy timer may not be stopped (Fixed in beta 7)
- Bug: CaCtrl: actions are never executed (Fixed in beta 7)
- Bug: Server Variables "HTTP_DAFLOGIN" is empty (Fixed in
beta 7)
- Bug: Basic Authentication: option Set Login/Password
cookies on successful logon does not work (Fixed in beta 7)
- Bug: Basic Authentication: "realm" string is always
"Protected Area" regardless the option set (Fixed in beta 7)
Version 5.0 beta 3 (2003/4/29)
- New: NT User Database added as a DAF User DB store
Version 5.0 beta 4 (2003/5/12)
- New: Per site DAF Data location support token #SiteID#
- New: DAF system logs may be disabled
- Change: Terme "Site Filter" was replaced by "Security Handler" (to avoid
confusion with ISAPI Filter and IP Filter)
- Permission requirments for configuration files may be read only for the
application pool identity
Version 5.0 beta 5 (2003/5/30)
- Change: XML configuration Path "HTMLLoginForm" replaced by "LoginForm"
- Change: XML configuration entry "HTMLLogin\UseLoginForm" replaced by
"LoginForm\LoginFormType"
- New: Log related to mapped NT accounts will show more details
Version 5.0 beta 6 (2003/7/22) / 6a (2003/7/30)
- Change: The filter with logon NT accounts with flag
LOGON32_LOGON_NETWORK_CLEARTEXT instead of LOGON32_LOGON_INTERACTIVE
- New: Cache entries may be cleared via an ASP script
- New: Cache option "Entry Time Limit" added
- New: Buttons "Clear all Entries" and "Clear Entry" added to the cache
configuration window
- Change: XML entry "Msg\URLLoginScript" changed to "Msg\LoginScriptUrl"
- Change: sub directory "dafdata" is no longer added systematically
to the path defined in the DAF Configuration Tool as the
DAF security handler data directory template. To use a DAF installation setup
with a previous version (beta 5 and older):
- if default template was used, you must enter this template
"#wwwrootiis#\..\daf#SiteID#\dafdata"
- if a custom template was used, you must end to your template path with
subdirectory "\dafdata"
- New: ISP Authorization Code implemented
- New: Site protection configuration via a web application implemented for
site owners in an ISP environment
- Change:Default Site ID for "DAFEngine" web site is now 100000 instead if
1000
- Bug: installation possible error:"MSVCP71.dll not found" (fixed in 5.0
beta 6a)
- Bug: DAF user names are not inserted in IIS logs (fixed in beta 7, build
5605)
- Bug in build 5606: HitCountMax error may be reported in place
of a DAFAUTH.INI error (fixed in beta 7)
Version 5.0 beta 7 (2003/11/16)
-
New: Tokens replacement supported in the protected area home page definition
(ex ?URL=#URL#) (build 5606)
- New: Session hit count max added (session collection
version 0x10001) (build 5606)
- New: Session error HTTP notification (build 5606)
- New: ODBC Advanced settings are set by default to -1
(=Automatic)
- New: [Simplified Properties] window added to the DAF
Configuration Tool
- New: Thread management optimized (thread are terminated
when idle)
- New: Session log off visible in the logs
- New: Second concurrent access maximum removed
- Bug: The log client (LOGCLIENT.EXE) may error popup with error
"SetThreadToken Failure". Fixed in beta 8
- Bug: While stopping a worker process an "EnterRead request at
\threadpool.cpp,291" error may be reported. Fixed in beta 8
- Bug: When a worker process is recycled, the work directory
"work\cmd\isa<PID>" is not removed. Fixed in beta 8
- Bug: When a worker process is recycled, an error 0x4C8 at mmf.cpp,202,
OpenMMFile, may be reported. Fixed in beta 8
- Bug: During a system shutdown, error popups may be displayed. Fixed in
beta 8
- Bug: Changes applied with the Configuration Tool are not active
immediately. Fixed in beta 8
- Bug: Security Handler/User ID & Session/Save Ticket ID in URL Query String
does not work. Fixed in beta 8
- Bug: When changing Security Handler log option "Log all received HTTP
requests" the new value is not activated after saving the settings (It is
needed to restarting the worker process). Fixed in beta 8.
- Bug: Login and Password automatically saved in cookies does not work
(cookies are not set) if user db log option "On Logon Sucess" is
disabled. Fixed in beta 8.
- Bug: If wrong Login and Password are stored in cookies, access to an
unprotected area is refused if option to read credentials in cookies is
enabled. Fixed in beta 8.
- Bug[215]:Various locks failure when a Security Handler and/or a User DB
are stopped/started while authentication requests are processed
- Bug[217]:Changes to a Security Handler or a User DB applied with the
Configuration Tool may not be active immediately. It is required to recycle
the worker process.
- New[218]:W3P processes ID list can be view with a browser
Version 5.0 beta 8 (2004/1/18)/build 5804 (2004/1/20)
- Bug[223]: When using an ODBC user database, errors are reported at user db
startup. Fixed in beta 8 build 5804
Version 5.0 beta 8 build 5805
Version 5.0 beta 9
Version 5.0 beta 9 build 5901
Version 5.0 beta 9 build 5902
Version 5.0 beta 9 build 5904 (2004/11/12)
Version 5.0 beta 9 build 5905 (2004/12/03)
- New[282]:HTTP Server user db data store added
- Bug[283]:Connection problems with remote DAF User DB fixed
Version 5.0 beta 9 build 5906 (2004/12/10)
Version 5.0 beta 9 build 5907 (2005/1/4)
- With HTML login forms accesses are denied (error reported refers to an
anonymous access) despite valid login/password pairs. Fixed in build 5909
Version 5.0 beta 9 build 5909 (2005/3/2)