SonicOS 8 Users
- SonicOS 8
- 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 Local Users and Groups
- Configuring Guest Services
- Configuring Guest Accounts
- Managing Guest Status
- SonicWall Support
Benefits of SonicWall SSO
SonicWall SSO is a reliable and time-saving feature that utilizes a single login to provide access to multiple network resources based on administrator-configured group memberships and policy matching. SonicWall SSO is transparent to end users and requires minimal administrator configuration.
By automatically determining when users have logged in or out based on workstation IP address traffic, or, for Terminal Services or Citrix, traffic from a particular user at the server IP address, SonicWall Single Sign-On (SSO) is secure and hands-free. SSO authentication is designed to operate with any external agent that can return the identity of a user at a workstation or Terminal Services/Citrix server IP address using a SonicWall Directory Connector-compatible protocol.
SonicWall SSO works for any service on the firewall that uses user-level authentication, including the Content Filtering Service (CFS), access rules, group membership and inheritance, and security services such as IPS, GAV, and Anti-Spyware inclusion/exclusion lists.
SonicWall SSO Agent can be installed on any Windows server on the LAN, and the TSA can be installed on any terminal server.
Other benefits of SonicWall SSO include:
| Ease of use | Users only need to sign in once to gain automatic access to multiple resources. |
| Improved user experience | Windows domain credentials can be used to authenticate a user for any traffic type without logging into the appliance using a Web browser. |
| Transparency to users | Users are not required to re-enter username and password for authentication. |
| Secure communication | Shared key encryption for data transmission protection. |
| Multiple SSO agents | Up to 8 agents are supported to provide capacity for large installations. |
| Multiple TSAs | Multiple terminal services agents (one per terminal server) are supported. The number depends on the model of the SonicWall Security Appliance and ranges from 8 to 512. |
| Login mechanism | Works with any protocol, not just HTTP. |
| Browser NTLM authentication | SonicWall SSO can authenticate users sending HTTP traffic without using the SSO Agent. |
| MacOS and Linux support | With Samba 3.5 and higher, SonicWall SSO is supported for Mac and Linux users. |
| Per-zone enforcement | SonicWall SSO can be triggered for traffic from any zone even when not automatically initiated by firewall access rules or security services policies, providing user identification in event logging or AppFlow Monitoring. |
Was This Article Helpful?
Help us to improve our support portal