-
Products
-
SonicPlatform
SonicPlatform is the cybersecurity platform purpose-built for MSPs, making managing complex security environments among multiple tenants easy and streamlined.
Discover More
-
-
Solutions
-
Federal
Protect Federal Agencies and Networks with scalable, purpose-built cybersecurity solutions
Learn MoreFederalProtect Federal Agencies and Networks with scalable, purpose-built cybersecurity solutions
Learn More - Industries
- Use Cases
-
-
Partners
-
Partner Portal
Access to deal registration, MDF, sales and marketing tools, training and more
Learn MorePartner PortalAccess to deal registration, MDF, sales and marketing tools, training and more
Learn More - SonicWall Partners
- Partner Resources
-
-
Support
-
Support Portal
Find answers to your questions by searching across our knowledge base, community, technical documentation and video tutorials
Learn MoreSupport PortalFind answers to your questions by searching across our knowledge base, community, technical documentation and video tutorials
Learn More - Support
- Resources
- Capture Labs
-
- Company
- Contact Us
The user is still authenticated by SSO even with bypass configuration
03/26/2020 
1,081 People found this article helpful
486,021 Views
Description
Troubleshooting: The user is still authenticated by SSO even with bypass configuration.
Resolution
In this scenario, the customer is trying to bypass certain machines from SSO authentication, even then those machines are authenticated by SSO. Those machines are shown as authenticated by SSO in user status. The customer has ULA rule configured for all LAN machines and that rule is not triggered.
- Navigate to Log | Log Monitor, follow the log trace to make sure if the SSO agent is the designated one which the customer uses to authenticate.
- Navigate to Firewall | Access Rules, select LAN to WAN in the Matrix to make sure the user level access rules are configured correctly.
In this case, there are two LAN to WAN access rules. The second one is the default one and it will not trigger the SSO authentication obviously. The first one, means all the trusted users want to access the WAN using http/https, will trigger SSO authentication. That is the reason why the machines are shown as authenticated by SSO in user status.
To resolve this issue there are two resolutions.
Resolution A:
If using the user level access to implement the SSO bypass, you need correct the access rules. In this case, PC2 with IP 192.168.205.136 is the SSO bypass machine.
1. For the second default LAN to WAN access rule, change the users included option from All to Everyone.
2. For the first LAN to WAN access rule, change the Source to the certain machine's IP. And if you choose the users/groups in the Users Included option rather than All, for instance Trusted Users, make sure option "Don't invoke Single Sign On to Authenticate Users" under Advanced tab is checked.
Resolution B:
Also you can use SSO Bypass feature under SSO configuration.
Step 1: Keep the LAN to WAN access rule configuration as default, that means just one access rule which passing all the traffic.
Step 2: Navigate to Users | Settings, click Configure SSO button, then click the Enforcement tab. Select LAN zone under Per-Zone SSO Enforcement. Then in the option "Bypass the Single Sign On process for traffic from" under SSO Bypass, select the certain machine's address object.
How to Test:
Before the SSO Bypass implement, both users zack555 on PC1 and zack666 on PC2 are authenticated by SSO.
While after SSO bypass implemented on PC2, try to access internet on PC2, the machine is not shown as authenticated by SSO in user status page.
Related Articles
- How to Block Google QUIC Protocol on SonicOSX 7.0?
- How to block certain Keywords on SonicOSX 7.0?
- How internal Interfaces can obtain Global IPv6 Addresses using DHCPv6 Prefix Delegation
Categories
- Firewalls > TZ Series
- Firewalls > SonicWall SuperMassive E10000 Series
- Firewalls > SonicWall SuperMassive 9000 Series
- Firewalls > SonicWall NSA Series
YES
NO