Configuring Web Settings > Configure Bypass Settings > Bypassing authentication settings
|
|
Bypassing authentication and filtering for internal networks. This option is available only if you have an I Series appliance, or a supported edge device that connects to the cloud service.
|
1.
|
2.
|
Enter a Name for the rule. This name appears in the Authentication Bypass list on the Bypass Settings page, and you can click on it at a later date to edit your settings.
|
3.
|
Select the Authentication method for the rule. Note that you can only select a fallback option for the authentication type configured in the policy - for example, if the policy specifies only NTLM identification, you can select Basic or No authentication, but not Form login.
|
|
Use defaults: Uses your default authentication method.
|
|
NTLM: Uses NTLM identification for the specified user agent(s) and destination(s). If an application is not NTLM-capable, basic authentication will be used instead. For more information about NTLM identification, see NTLM transparent identification.
|
|
Form login: Displays the secure login form to users before they use their cloud credentials to proceed over a secure connection. For more information, see Access Control tab.
|
|
Basic: Uses the basic authentication mechanism supported by many web browsers. No welcome page is displayed. For more information on basic authentication, see Access Control tab.
|
|
Welcome page: Displays a welcome page to users before they use basic authentication to proceed. The welcome page is configurable in each policy on the Access Control tab. Note that the welcome page is not available for traffic from I Series appliances. For more information, see Pre-logon welcome page.
|
|
No authentication: Bypasses all authentication and identification methods in the cloud. Select this option for Internet applications that are incapable of authentication.
|
4.
|
Content filtering is enabled by default. Optionally, you can bypass all content filtering for the specified user agent(s) and destination(s) by selecting Disabled.
|
We strongly recommend you do not disable content filtering unless it is for applications and sites that do not work with the cloud service and that you trust implicitly. Disabling content filtering overrides all other filtering rules, including web category filtering actions. This means that all content is allowed. This could allow viruses and other malware into your network.
|
|
To apply the rule to all user agents, select All user agents. You might want to do this if you are setting up a custom rule that applies to all browsers on all operating systems in your organization.
|
|
If you want to apply the bypass rule to one or more user agents, select Specific user agents, and enter each user agent on a separate line. Use the asterisk wildcard to match one line to multiple user agent strings, for example Mozilla/5.0*.
|
|
To match against all domains and URLs, select All destinations. You might want to do this if you are setting up a custom rule that applies to a specific user agent that accesses multiple sites.
|
|
To apply the rule to one or more sites, select Specific destinations, and enter each URL or domain on a separate line. URLs must include the protocol portion (http://) at the beginning and a forward slash (/) at the end - for example, http://www.google.com/. If these elements are not present, the string is treated as a domain. Domains cannot include a forward slash at the end - for example, mydomain.com.
|
7.
|
Click Save.
|
1.
|
2.
|
Enter a Name for the rule. This name appears in the internal networks list on the Bypass Settings page, and you can click on it at a later date to edit your settings.
|
3.
|
Select the Authentication method for the rule. Note that you can only select a fallback option for the authentication type configured in the policy - for example, if the policy specifies NTLM identification, you can select Basic or No authentication, but not Form login.
|
|
Use defaults: Uses your default authentication method.
|
|
NTLM: Uses NTLM identification for the specified internal network(s). If an application is not NTLM-capable, basic authentication will be used instead. For more information about NTLM identification, see NTLM transparent identification.
|
|
Form login: Displays the secure login form to users before they use their cloud credentials to proceed over a secure connection. For more information, see Access Control tab.
|
|
Basic: Uses the basic authentication mechanism supported by many web browsers. No welcome page is displayed. For more information on basic authentication, see Access Control tab.
|
|
No authentication: Bypasses all authentication and identification methods in the cloud service. Select this option for internal networks that should never use authentication credentials.
|
4.
|
Content analysis is enabled by default. Optionally, you can bypass all filtering for the specified internal network(s) by selecting Disabled.
|
We strongly recommend you do not disable content filtering unless it is for applications and sites that do not work with the cloud service and that you trust implicitly. Disabling content filtering overrides all other filtering rules, including web category filtering actions. This means that all content is allowed. This could allow viruses and other malware into your network.
|
d.
|
Click OK when you are done.
|
6.
|
Click Save.
|
Configuring Web Settings > Configure Bypass Settings > Bypassing authentication settings
|