Note: This topic applies to the Edinburgh Release.
Note: By default, Guardian comes with an authentication policy in place. To use it, you configure your users’ web browsers to use Guardian as their web proxy. For more information, see Creating a Non-transparent Connection Manually.
Guardian uses authentication to:
|||Identify users and assign them to groups, so that Guardian can apply different policies to each group|
|||Allow access to registered users or trusted workstations|
|||Provide logging and auditing facilities in case of misuse|
|||Show in real time which users are accessing content|
An authentication policy is comprised of a connection type, an authentication method, port information and a location.
Guardian can use several different authentication methods to identify a user or group, with different requirements and restrictions. Authentication policies determine which method is used. They also determine which interfaces and ports Guardian listens on for web requests.