|
|
·
|
·
|
·
|
·
|
·
|
·
|
|
The log files are very detailed. They show all user
activities, when logged in, from where, from what kind of
system, what role was selected, what services were
activated and when, etc. It is also possible to get
extended information about several application protocols
such as for FTP and NetBIOS about what files were transferred,
even including all data if desired.
|
|
Yes. It is possible to specify that one category of
users should have access to, for example,
www.company.com/sales and another category to
www.company.com/support. This functionality relieves
web servers from having to do user authorization and can
save both work and equipment.
|
|
The AppGate server can offer a virtual printer to all
application servers. All printouts are stored on the
AppGate server and when a user who owns a printout
logs in, it can be automatically downloaded to the user’s
workstation and sent to a local printer without user interaction.
There is a product sheet available that describes
the secure local print module.
|
|
Yes, the AppGate server keeps a list that tells where
to search for user accounts. It searches all servers until
the user account is found. A typical list can be: internal
database; an external LDAP server; an RSA Authentication
Manager (formerly named ACE server, used for
SecurID authentication); and finally an Active Directory
server.
Users may also be given the choice to use one or
more authentication methods, and the available services
may then depend on what method is being used.
|
|
Yes, it is easy to specify how groups found in AD or
LDAP should be mapped into AppGate user roles. This is
very convenient in situations where user administration
and rights management should be separated from the
details about what services each category of users should
have access to. The AppGate database then tells how
each category of users should be mapped into various
services.
|
|