18.06.2014 Views

iPrism Administration Guide - EdgeWave

iPrism Administration Guide - EdgeWave

iPrism Administration Guide - EdgeWave

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

The Big Picture<br />

• IM/P2P Profiles filter IM and P2P usage.<br />

Each profile is associated with a group of users. One way of identifying<br />

users is by the IP address of the machine they are using. For example, you<br />

can define a profile called “Sales” which contains all the addresses in the<br />

range 192.168.77.0 to 192.168.77.255.<br />

Users can also be identified by a user name and password through an<br />

authentication process. There are a number of authentication systems<br />

available including NTLM (for Microsoft Windows users) and LDAP (for<br />

UNIX, Linux, and Novell users).<br />

Finally, you can manually add users to your <strong>iPrism</strong>. In practice, manual<br />

creation is usually only done for <strong>iPrism</strong> administrators and subadministrators.<br />

Assigning Profiles<br />

Now that have set up profiles, you need to learn how to associate a profile<br />

with the people to which it applies. The simplest way of doing this is to<br />

assign a profile to a set of IP addresses. Anyone using a machine which has<br />

one of these addresses will be assigned the same profile. This is useful when<br />

you have a lot of public or lab machines and wish to apply the same profile<br />

to everyone in the room. For example, if you’re running a school, you can<br />

assign a profile called “KidSafe” to all the machines in the student lab, and<br />

assign a profile called “NoBlocking” to the teacher’s offices.<br />

You can also assign profiles to a set of authentication users. (Authentication<br />

means that you have a username to work with which has been validated by a<br />

password.) Although each web access message contains the IP address of<br />

the computer making the request, there is no user identification included in<br />

the message. 1<br />

The <strong>iPrism</strong> system interfaces with Windows NTLM authentication as well<br />

as LDAP which is used UNIX, Linux, Novel. If you want to use “user<br />

level” authentication, Chapter 6: Users and Authentication contains simple,<br />

step-by-step instructions which will help you get your <strong>iPrism</strong> working with<br />

1. This is not always true. If you configure your <strong>iPrism</strong> and user computers just right, you<br />

can create a system where each web access message will contain user identification. This<br />

complex form of configuration is discussed in Chapter 6: Users and Authentication.<br />

16<br />

<strong>iPrism</strong> <strong>Administration</strong> <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!