SonicOS 7.1 Users
- SonicOS 7.1
- About SonicOS
- About User Management
- Using Local Users and Groups for Authentication
- Using RADIUS for Authentication
- Using LDAP/Active Directory/eDirectory Authentication
- Using RADIUS
- Using TACACS+
- Using Single Sign-On
- What is Single Sign-On?
- Benefits of SonicWall SSO
- Platforms and Supported Standards
- How Does Single Sign-On Work?
- How Does SSO Agent Work?
- How Does Terminal Services Agent Work?
- How Does Browser NTLM Authentication Work?
- How Does RADIUS Accounting for Single-Sign-On Work?
- Installing the Single Sign-On Agent and/or Terminal Services Agent
- Single Sign-On Advanced Features
- Configuring Access Rules
- Managing SonicOS with HTTP Login from a Terminal Server
- Viewing and Managing SSO User Sessions
- Multiple Administrator Support
- Configuring Users Status
- Configuring User Settings
- User Login Settings
- Setting the Authentication Method for Login
- Configuring RADIUS Authentication
- Configuring LDAP
- Configuring TACACS+
- Requiring User Names be Treated as Case-Sensitive
- Preventing Users From Logging in from More than One Location
- Forcing Users to Log In Immediately After Changing Their Passwords
- Displaying User Login Information Since the Last Login
- Setting the Single-Sign-On Methods
- One-Time Password Settings
- Configuring the User Web Login Settings
- Adding URLs to Authentication Bypass
- User Session Settings
- Accounting
- [[[Missing Linked File System.LinkedTitle]]]
- User Login Settings
- Configuring and Managing Partitions
- Configuring Local Users and Groups
- Configuring Guest Services
- Configuring Guest Accounts
- Managing Guest Status
- SonicWall Support
Adding URLs to Authentication Bypass
SonicOS Guest Services allows guest users to have access through your network directly to the Internet without access to your protected network. To do this, SonicOS uses the IP address of the user’s computer.
Using the IP address as the identifier is useful when guest user traffic passes through a network router, as this changes the source MAC address to that of the router. However, the user’s IP address passes through unchanged.
If only the MAC address is used for identification, two clients behind the same router have the same MAC address upon reaching the network security appliance. When one client gets authenticated, the traffic from the other client is also treated as authenticated and bypasses the guest service authentication.
By using the client IP address for identification, all guest clients behind the routed device are required to authenticate independently.
To add HTTP URLs user authentication bypass in Access Rules
- Navigate to Device > Users > Settings > Authentication Bypass.
- Click Add. The Add URL page displays.
- In the Add URL field, enter the URL.
- Click Add. A change order pop-up confirmation displays.
- Click OK.
- Click Accept.
Was This Article Helpful?
Help us to improve our support portal