Authenticated, Controlled Access
The NetCache provides authenticated access to caching services, authorized
at the user and group level, based on rules specified for each protocol.
Start by configuring Authentication
Settings (left) to allow, deny, or authenticate users for HTTP,
SSL, FTP, NNTP, or Gopher. Authentication can rely on a local user
database or an existing LDAP server or group of RADIUS servers. Integration
with external auth servers is important to eliminate re-entry of user
data in the NetCache.
Next, use the Add / Delete
User page (right) to configure username, password, and permission
to use proxy and management ports. Access control lists (ACLs) can
be applied to user groups, created with the Add / Delete Group page.
Groups can be used to restrict client IP addresses and limit the URLs
they can access. But beware: permissions and ACLs are ignored unless
authentication has been enabled for the affected protocol.
We created a user with permission for authenticated FTP access, and enabled
FTP authentication. Thereafter, any client requesting an ftp://
URL was prompted for login/password, and only the user we had created was
granted access.
ACLs can also be defined globally, and per protocol,
using the Access Control Settings page (left). The NetCache
supports a complex, powerful syntax for defining ACLs. Regular expressions
can be used to control access by client or server IP, URL, time of
day, user, group, protocol, and category. Actions control default
behavior: permit (the default default), deny, or require authentication.
Requests that fail authentication can be rewritten or redirected.
NetCache access controls are more granular than those we've seen in
other caching products. While enterprises will benefit more from individual
user-level ACLs, ISPs can employ group or protocol-level ACLs to create
value-added services. We note that user/group-level authenticated access
control to multimedia services is not provided in the version tested.