13.07.2015 Views

Web Security Deployment Guide (PDF) - Websense

Web Security Deployment Guide (PDF) - Websense

Web Security Deployment Guide (PDF) - Websense

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.

General <strong>Deployment</strong> RecommendationsSun Java System Directory ServerNovell Directory Services/Novell eDirectoryFor information on configuring <strong>Web</strong>sense software to communicate with a supporteddirectory service, see the <strong>Web</strong>sense Manager Help. <strong>Web</strong>sense software does not needto run on the same operating system as the directory service.Deploying transparent identification agentsIf you are using <strong>Web</strong>sense software in stand-alone mode, or if your integrationproduct does not send user information to <strong>Web</strong>sense software, use <strong>Web</strong>sensetransparent identification agents to identify users without prompting them for a username and password.There are 4 optional transparent identification agents:DC AgenteDirectory AgentLogon AgentRADIUS AgentNoteDC Agent must have domain administrator privileges toretrieve user logon information from the domaincontroller.If you have deployed <strong>Web</strong>sense software in a single network location, a singletransparent identification agent instance is recommended.In deployments that cover multiple locations, you can install an agent instance inmultiple domains.For example:One DC Agent instance can handle multiple trusted domains. Add additionalinstances based on:• The load placed on DC Agent• Whether a DC Agent instance can see all the domains on the network,including remote officesLoad results from the number of user logon requests. If the network is large(10,000+ users, 30+ domains), having multiple DC Agent instances allows forfaster identification of users.If multiple Filtering Services are installed, each Filtering Service instance must beable to communicate with all DC Agent instances.One eDirectory Agent is required for each eDirectory Server.<strong>Deployment</strong> <strong>Guide</strong> 31

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

Saved successfully!

Ooh no, something went wrong!