About authentication policies
Note: The Smoothwall Filter comes with an authentication policy in place by default. However, to use it, you need to configure your users’ web browsers to use the Smoothwall Filter as their web proxy, see our knowledge base article, When to use Non-Transparent Authentication Policies.
Authentication policies determine how user credentials are obtained from the browser before allowing the user to browse. They are specific to your organization's needs.
You can create nontransparent and transparent authentication policies. With a transparent authentication policy, you can apply a web filter policy and authentication to a user, or group of users, whose devices’ network connection uses the Smoothwall Filter function. With nontransparent authentication policies, you can apply a web filter policy and authentication to a user, or group of users, whose web browsers are configured to connect to the Internet using the Smoothwall Filter function as their web proxy.
The Smoothwall Filter uses authentication to:
- Identify users and assign them to groups, so that the Smoothwall Filter can apply different policies to each group.
- Allow access to registered users or trusted devices.
- Provide logging and auditing facilities in case of misuse.
- Show the users accessing content in real time.
An authentication policy is comprised of a connection type, an authentication method, port information and a location.
The Smoothwall Filter can use several different authentication methods to identify a user or group, with different conditions and restrictions. Authentication policies determine the method used. They also determine the interfaces and ports listened on for web requests.
Default Authentication Policy
The Smoothwall Filter comes with the following authentication policy ready for use:
- Non-transparent authentication policy — Any user’s browser configured to use the Smoothwall Filter on port 800 because its web proxy has this authentication policy applied to it. To create more authentication policies, see the help topic, Creating authentication policies.