• SonicOS 7.0 Users
• About User Management
  • Using Local Users and Groups for Authentication
    • About User Databases
    • About User Groups
  • Using RADIUS for Authentication
  • Using LDAP/Active Directory/eDirectory Authentication
    • LDAP Terms
    • LDAP Directory Services Supported in SonicOS
    • LDAP User Group Mirroring
      • Integrating LDAP into the SonicOS Network Security Appliance
        • Preparing Your LDAP Server for Integration
        • Configuring the CA on the Active Directory Server
        • Exporting the CA Certificate from the Active Directory Server
        • Importing the CA Certificate into SonicOS
      • LDAP Group Membership by Organizational Unit
  • 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?
      • SonicWall SSO Authentication Using the SSO Agent
      • SonicWall SSO Authentication Using the Terminal Services Agent
      • SonicWall SSO Authentication Using Browser NTLM Authentication
    • How Does SSO Agent Work?
      • Logging
    • How Does Terminal Services Agent Work?
      • Multiple TSA Support
      • Encryption of TSA Messages and Use of Session IDs
      • Connections to Local Subnets
      • Non-Domain User Traffic from the Terminal Server
    • How Does Browser NTLM Authentication Work?
      • NTLM Authentication of Domain Users
      • NTLM Authentication of Non-Domain Users
      • Credentials for NTLM Authentication in the Browser
    • How Does RADIUS Accounting for Single-Sign-On Work?
      • RADIUS Accounting Messages
      • SonicWall Compatibility with Third-Party Network Appliances
      • Proxy Forwarding
      • Non-Domain Users
      • IPv6 Considerations
      • RADIUS Accounting Server Port
    • Installing the Single Sign-On Agent and/or Terminal Services Agent
      • Installing the SonicWall SSO Agent
      • Installing the SonicWall Terminal Services Agent
        • Accessing the SonicWall Terminal Services Agent
        • Creating a SonicWall TSA Troubleshooting Report
    • Single Sign-On Advanced Features
      • Viewing SSO Mouseover Statistics
      • Using the Single Sign-On Statistics in the TSR
      • Examining the Agent
      • Remedies
    • Configuring Access Rules
      • Automatically Generated Rules for SonicWall SSO
      • Accommodating Mac and Linux Users
        • Using SSO on Mac and Linux With Samba
        • Using SSO on Mac and Linux Without Samba
      • Allowing ICMP Pings from a Terminal Server
    • Managing SonicOS with HTTP Login from a Terminal Server
    • Viewing and Managing SSO User Sessions
      • Logging Out SSO Users
      • Configuring Additional SSO User Settings
      • Viewing SSO and LDAP Messages with Packet Monitor
      • Capturing SSO Messages
      • Capturing LDAP Over TLS Messages
    • Multiple Administrator Support
      • Preempting Administrators
      • Logging in with Administrator Rights
        • Disabling the User Login Status Popup
      • Configuring Multiple Administrator Support
        • Configuring Additional Administrator User Profiles
        • Configuring Administrators Locally when Using LDAP or RADIUS
        • Verifying Multiple Administrators Support Configuration
        • Viewing Multiple Administrator Related Log Messages
• Configuring Users Status
  • Displaying Inactive Users
  • Displaying Unauthenticated Users
  • Displaying the User Count
  • Refreshing the Users List
  • Logging Out Users
    • Logging Out a Single User
    • Logging Out Multiple Users
• Configuring User Settings
  • User Login Settings
    • Setting the Authentication Method for Login
    • Configuring RADIUS Authentication
      • Configuring RADIUS Settings
      • Configuring RADIUS Users Settings
      • Testing RADIUS Settings
    • Configuring LDAP
      • Configuring LDAP Setting
      • Configuring Referrals
      • LDAP User Settings
      • Enabling LDAP Relay
      • Testing LDAP Settings
    • Configuring TACACS+
      • Configuring TACAS+ Settings
      • Configuring TACACS+ User Settings
      • Testing TACACS+ Settings
    • 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
    • Configuring SSO
      • SSO Agents
      • Users
      • Enforcement
      • Terminal Services
      • NTLM
      • RADIUS Accounting
      • 3rd Party API
      • Capture Client
      • Test
  • One-Time Password Settings
  • Configuring the User Web Login Settings
    • Setting the Timeout for the Authentication Page
    • Setting How the Browser is Redirected
    • Managing Redirections to the Login Page
    • Using a CHAP challenge to Authenticate Users
    • Redirecting Unauthenticated Users
    • Authenticating user's multiple IP addresses
  • Adding URLs to Authentication Bypass
  • User Session Settings
    • User Session Settings for SSO-Authenticated Users
    • User Session Settings for Web Login
  • Accounting
    • Configuring RADIUS Accounting
      • Sending RADIUS Accounting Information to Servers
      • Configuring User Accounting
      • Testing RADIUS Accounting
      • Editing RADIUS Servers
      • Deleting RADIUS Servers
    • Configuring TACACS+ Accounting
      • Configuring User Accounting
      • Testing TACACS Accounting
      • Editing TACACS Servers
      • Deleting TACACS Servers
  • [[[Missing Linked File System.LinkedTitle]]]
    • • Post-Login Acceptable Use Policy Example Template
      • Post-Login Acceptable Use Policy Preview Message
• Configuring and Managing Partitions
  • Authentication Partitioning Settings
  • Authentication Partitions
    • Adding Partitions and Subpartitions
    • Editing Partitions
    • Deleting Partitions and Subpartitions
      • Deleting All Partitions
      • Deleting Multiple Partitions
      • Deleting a Single Partition
  • Assigning Servers, Agents, and Clients
    • Manually Assigning Servers, Agents, and Clients
    • Automatically Assigning Servers, Agents, and Clients
  • Partition Selection Policies
    • Adding Partition Policies
    • Deleting Partitions Policies
      • Deleting All Partitions Policies
      • Deleting Multiple Partitions Policies
      • Deleting a Single Partition Policiy
• Configuring Local Users and Groups
  • About Authentication and Passwords
    • Using Two-Factor Authentication
    • Enforcing First Login Password Change
  • Configuring Local Users
    • Quota Control for all Users
    • Viewing Local Users
    • Adding Local Users
      • Configuring Local Users Settings
      • Configuring Local Users Groups
      • Configuring Local Users VPN Access
      • Configuring Local Users User Quota
    • Editing Local Users
  • Configuring Local Groups
    • Adding Local Groups
      • Configuring Local Groups Settings
      • Configuring Local Group Settings Members
      • Configuring Local Group Settings VPN Access
      • Configuring Local Group Settings Administration
    • Editing Local Groups
  • Settings
• Configuring Guest Services
  • Adding Guest Profiles
  • Editing Guest Profiles
  • Deleting Guest Profiles
• Configuring Guest Accounts
  • Adding Guest Accounts
  • Editing Guest Accounts
  • Deleting Guest Accounts
    • Deleting a Guest Account
    • Deleting Multiple Guest Accounts
    • Deleting All Guest Accounts
• Managing Guest Status
  • Logging Out Guests
  • Logging Out All Guests
• SonicWall Support
  • About This Document

Encryption of TSA Messages and Use of Session IDs

The TSA uses a shared key for encryption of messages between the TSA and the firewall when the user name and domain are contained in the message. The first open notification for a user is always encrypted, because the TSA includes the user name and domain.

The shared key is created in the TSA, and the key entered in the firewall during SSO configuration must match the TSA key exactly.

The TSA includes a user session ID in all notifications rather than including the user name and domain every time. This is efficient, secure, and allows the TSA to re-synchronize with Terminal Services users after the agent restarts.