If you wish you can configure user authentication on the FB itself. After this you need to enable logging on the FB services and then you can use historical report to get details about user activity. Historical reports would not give you the minutest of the details but would give you some, you can deploy and check if that meets your requirement.
To authenticate, clients must connect to the authentication server using a Java-enabled Web browser pointed to:
http://IP address of any Firebox interface:4100/
A Java applet loads a prompt for a username and password that it then passes to the authentication server using a challenge-response protocol. Once successfully authenticated, users minimize the Java applet and browser window and begin using allowed network services.As long as the Java window remains active (it can be minimized but not closed) and the Firebox does not reboot, users remain authenticated until the session times out. To prevent an account from authenticating, disable the
account on the authentication server.
The WatchGuard Firebox System can authenticate users against any of five authentication server types:
" A built-in authentication server on the Firebox
" NT primary domain controllers
" RADIUS-compliant authentication servers
" CRYPTOCard authentication servers
" SecurID authentication servers
To specify authentication type:
1 From Policy Manager, select Setup => Firewall Authentication.
2 In the Authentication Enabled Via box, select the authentication server you want you use.
3 In Logon Time-out, select how many seconds are allowed for an attempted logon before the time-out
shuts down the connection.
4 In Session Time-out, set how many hours a session can remain open before the time-out shuts down the connection. This is a set time limit regardless of enduser traffic.
Main Topics
Browse All Topics
by: bloodymalth5Posted on 2007-06-22 at 06:31:24ID: 19341093
You can look at this one
http://www.wavecrest.net/s
or this one
http://www.smartfilter.com