Scenario 2: Route all traffic through the

BlackBerry Proxy

and then through a web proxy server

This configuration is appropriate for organizations that require all traffic from work apps to be routed internally. A web proxy server is required for internal servers to connect to the internet.

For example, connections to public sites like google.com and microsoft.com as well as internal

Microsoft Exchange Server

s and

SharePoint

servers must all be routed internally through the

BlackBerry Proxy

.

In this configuration, it is assumed that a web proxy server connection to the Internet is also required, because most organizations that require all traffic to be routed internally also require that traffic be routed through a web proxy server for filtering or monitoring.

BlackBerry Dynamics

connectivity profile

Set the
Default allowed domain route type
to
BlackBerry Proxy cluster
.
(Optional) Add internal domains to the
Allowed domains
list. This is not necessary when the
Default allowed domain route type
is set to route through the
BlackBerry Proxy
.
(Optional) Add specific server names under
Additional servers
and select a
BlackBerry Proxy
cluster. This is not necessary when the
Default allowed domain route type
is set to route through the BlackBerry Proxy.
(Optional) If you want specific servers to be exempt from the default routing through the
BlackBerry Proxy
, you can specify specific domains (either under
Allowed domains
or
Additional servers
) and select
Direct
. This allows you to route most traffic through
BlackBerry Proxy
but exempt some traffic (for example, to improve performance to certain trusted public sites).

See BlackBerry Dynamics connectivity profile settings for more information about how the rules in the connectivity profile are used.

Depending on the complexity of your environment, you can configure the

BlackBerry Proxy

server to route traffic through a web proxy server rather than directly to the destination server.

You can either use a manual web proxy server configuration or a PAC file.

Manual HTTP proxy:

Manual web proxy server configuration is sufficient if there are no complex rules governing which URLs should use a web proxy server and which should go direct. If all traffic should use a web proxy server, then configuring a manual web proxy server is the easiest way to accomplish this.

Enable the manual HTTP proxy:
In an on-premises environment	Go to Settings > Infrastructure > BlackBerry Router and proxy . Expand Global Settings , and select Enable manual HTTP proxy .
In a Cloud environment	Go to Settings > BlackBerry Dynamics > Clusters . Click on the cluster you want to edit. Enable Override Global Settings , and select Enable manual HTTP proxy .
Select
Use proxy to connect to all servers
.
Type the address and port for the web proxy server.

Proxy auto-configuration (PAC) file:

If your organization requires more complex rules about which servers should use a proxy and which should connect directly, BlackBerry recommends using a PAC file because it is much easier to manage.

For example, if you want all connections to the public internet to use the web proxy server, but all internal domains to connect directly, the best practice is to use a PAC file.

Open the proxy settings:
In an on-premises environment	Go to Settings > Infrastructure > BlackBerry Router and proxy .
In a Cloud environment	Go to General Settings > BlackBerry Router and proxy .
Expand
Global Settings
, select
Enable PAC
.
Enter the PAC URL and authentication information as required.

No app-specific proxy configurations are necessary. This configuration assumes that all traffic is routed internally and either a manual proxy or PAC is configured at the

BlackBerry Proxy

server.