Effects of Enabling Watchguard Active Directory authentication

I need to configure my firewall/server to grant access to certain websites based on the USER, and the only way I can see to do this is through WebBlocker policies on our WatchGuard firewall. From my research, I understand that to do it I first would have to set up active directory authentication  which is not currently enabled.  I need to know how enabling this would affect the users experience.

Will enabling this require them to authenticate  each time they open a browser window?

Thanks for your help.

bjwestAsked:
Who is Participating?
 
dpk_walConnect With a Mentor Commented:
Active directory is not the only way; however it would be a preferred way for most of the administrators as it requires less configuration in terms of user addition and password maintenance.
Webblocker and restrictive website access are two different options. If you enable webblocker you can explicitly deny a website or category or permit the same or even create exceptions.

When you create multiple HTTP services (packet or proxies) for varied internet access, then depending on the access the polciies would be enforced. If you have a less restrictive policy allowing all internet access then all traffic would go out through that policy instead.

Enabling AD authentication on firebox and then configuring a policy which allows access post authentication; this would force them to first authenticate on a java based applet. In the latest versions they can have single-sign-on enabled; otherwise moment the java applet window is closed; they would need to authenticate again.

Please let know if you need more details.

Thank you.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.