The Dell SonicWALL SRA Administrator’s Guide provides network administrators with a highlevel overview of Dell SonicWALL SRA technology, including activation, configuration, and
administration of the Dell SonicWALL SRA management interface and the Dell SonicWALL
SRA appliance.
Always check <http://www.sonicwall.com/support/documentation.html> for the latest version of
this guide as well as other Dell SonicWALL products and services documentation.
Guide Conventions
The following conventions are used in this guide:
ConventionUse
BoldHighlights field, button, and tab names. Also highlights
Chapter 1
About This Guide
window, dialog box, and screen names. Also used for file names
and text or values you are being instructed to type into the interface.
ItalicIndicates the name of a technical manual, emphasis on certain
words in a sentence, or the first instance of a significant term or
concept.
Menu Item > Menu ItemIndicates a multiple step Management Interface menu choice. For
example, System > Status means select the Status page under
the System menu.
About This Guide | 9
10 | SRA 6.0 Administrator’s Guide
This chapter provides an overview of the Dell SonicWALL SRA technology, concepts, basic
navigational elements and standard deployment guidelines. This chapter includes the following
sections:
•“Overview of Dell SonicWALL SRA” section on page 11
•“Concepts for Dell SonicWALL SRA” section on page 18
•“Navigating the SRA Management Interface” section on page 71
•“Deployment Guidelines” section on page 79
Overview of Dell SonicWALL SRA
The Dell SonicWALL SRA appliance provides organizations with a simple, secure and
clientless method of access to applications and network resources specifically for remote and
mobile employees. Organizations can use SRA connections without the need to have a preconfigured, large-installation host. Users can easily and securely access email files, intranet
sites, applications, and other resources on the corporate Local Area Network (LAN) from any
location by accessing a standard Web browser.
Chapter 2
SRA Overview
This section contains the following subsections:
•“SSL for Virtual Private Networking (VPN)” section on page 11
•“SRA Virtual Appliance” section on page 12
•“SRA Software Components” section on page 12
•“SRA Hardware Components” section on page 13
SSL for Virtual Private Networking (VPN)
A Secure Socket Layer-based Virtual Private Network (SSL VPN) allows applications and
private network resources to be accessed remotely through a secure connection. Using SSL
VPN, mobile workers, business partners, and customers can access files or applications on a
company’s intranet or within a private local area network.
Organizations use Virtual Private Networks (VPNs) to establish secure, end-to-end private
network connections over a public networking infrastructure, allowing them to reduce their
communications expenses and to provide private, secure connections between a user and a
site in the organization. By offering Secure Socket Layer (SSL) VPN, without the expense of
special feature licensing, the SRA appliance provides customers with cost-effective
alternatives to deploying parallel remote-access infrastructures.
SRA Overview | 11
SRA Virtual Appliance
The SRA Virtual Appliance is a virtual machine that runs the SRA series software on a VMware
platform. All software components, features, and functionality described in this guide are
supported by the SRA Virtual Appliance, except High Availability and SSL Offloading.
Deploying the SRA as a virtual appliance allows leveraging of shared computing resources to
optimize utilization, easy migration and reduced capital costs. The SRA Virtual Appliance
provides the following benefits:
•Cost savings:
–
Multiple virtual machines can run on a single server, reducing hardware costs, power
consumption, and maintenance costs.
–
Microsoft Windows Server is not required, eliminating the cost of the Windows license.
•Operational ease:
–
In a virtual environment, it is easy to commission new servers or decommission old
ones, or to bring servers up or down.
–
Installation is accomplished by importing a file into the virtual environment, with no
need to run an installer.
•Security:
–
The SRA Virtual Appliance provides the same hardened operating system that comes
with the SRA hardware appliances.
The elements of basic VMware structure must be implemented prior to deploying the SRA
Virtual Appliance. For detailed information about deploying the SRA Virtual Appliance, see the
Dell SonicWALL SRA Virtual Appliance Getting Started Guide, available at:
http://www.sonicwall.com/us/support/3893.html
SRA Software Components
SRA appliances provide clientless identity-based secure remote access to the protected
internal network. Using the Virtual Office environment, SRA appliances can provide users with
secure remote access to your entire private network, or to individual components such as File
Shares, Web servers, FTP servers, remote desktops, or even individual applications hosted on
Citrix or Microsoft Terminal Servers.
Although SRA protocols are described as clientless, the typical SRA portal combines Web,
Java, and ActiveX components that are downloaded from the SRA portal transp arently , allowing
users to connect to a remote network without needing to manually install and configure a VPN
client application. In addition, SRA enables users to connect from a variety of devices, including
Windows, Macintosh, and Linux PCs. ActiveX components are only supported on Windows
platforms.
For administrators, the SRA Web-based management interface provides an end-to-end SSL
VPN solution. This interface can configure SRA users, access policies, authentication methods,
user bookmarks for network resources, and system settings.
For clients, Web-based SRA customizable user portals enable users to access, update, upload,
and download files and use remote applications installed on desktop machines or hosted on an
application server. The platform also supports secure Web-based FTP access, network
neighborhood-like interface for file sharing, Secure Shell versions 1 and 2 (SSHv1) and
(SSHv2), Telnet emulation, VNC (Virtual Network Computing) and RDP (Remote Desktop
Protocol) support, Citrix Web access, bookmarks for offloaded port als (external Web sites), and
Web and HTTPS proxy forwarding.
12 | SRA 6.0 Administrator’s Guide
The SRA network extension client, NetExtender, is available through the SRA Web portal via an
ActiveX control on Windows or using Java on MacOS or Linux systems. It is also available through
sta nd -al on e ap pl ic ati on s f or W in dow s, Lin ux , a nd M ac OS p la tf or ms. The NetExtender standalone
applications are automatically installed on a client system the first time the user clicks the
NetExtender link in the Virtual Office portal. SRA NetExtender enables end users to connect to
the remote network without needing to install and configure complex software, providing a
secure means to access any type of data on the remote network. NetExtender supports IPv6
client connections from Windows systems running Vista or newer, and from Linux clients.
Note
The SSHv2 applet requires SUN JRE 1.6.0_10 or higher and can only connect to a server
that supports SSHv2. The RDP Java applet requires SUN JRE 1.6.0_10 or higher. Telnet,
SSHv1 and VNC applets support MS JVM in Internet Explorer, and run on other browsers
with SUN JRE 1.6.0_10 or higher.
SRA Hardware Components
See the following sections for descriptions of the hardware components on SRA appliances:
•“SRA 4600 Front and Back Panels Overview” on page 14
•“SRA 1600 Front and Back Panels Overview” on page 15
•“SRA 4200 Front and Back Panels Overview” on page 16
•“SRA 1200 Front Panel Overview” on page 17
SRA Overview | 13
SRA 4600 Front and Back Panels Overview
Console Port: Provides
serial access to console
messages.
USB Ports:
(for future use)
Reset Button
Power LED
Test LED
Alarm LED
X0: Gigabit Ethernet
Default management port.
Provides connectivity between
the SRA and your gateway.
X1:
Gigabit Ethernet
X2:
Gigabit Ethernet
X3:
Gigabit Ethernet
Exhaust fan
Power plug
Power switch
Figure 1SRA 4600 Front and Back Panels
Table 1SRA 4600 Front Panel Features
Front Panel FeatureDescription
Console PortRJ-45 port, provides access to console messages with serial connec-
USB PortsProvides access to USB interface (for future use).
Reset ButtonProvides access to SafeMode.
Power LEDIndicates the SRA 4600 is powered on.
Test LEDIndicates the SRA 4600 is in test mode.
Alarm LEDIndicates a critical error or failure.
X3Provides access to the X3 interface and to SRA resources.
X2Provides access to the X2 interface and to SRA resources.
X1Provides access to the X1 interface and to SRA resources.
X0Default management port. Provides connectivity between the SRA
Table 2SRA 4600 Back Panel Features
14 | SRA 6.0 Administrator’s Guide
Back Panel FeatureDescription
Exhaust fanProvides optimal cooling for the SRA 4600 appliance.
Power plugProvides power connection using supplied power cord.
Power switchPowers the SRA 4600 on and off.
tion (115200 Baud). Provides access to command line interface (for
future use).
4600 and your gateway.
SRA 1600 Front and Back Panels Overview
Console Port: Provides
serial access to console
messages.
USB Ports:
(for future use)
Reset Button
Power LED
Test LED
Alarm LED
X0: Gigabit Ethernet
Default management port.
Provides connectivity between
the SRA and your gateway.
X1:
Gigabit Ethernet
Exhaust fanPower switch
Power plug
Figure 2SRA 1600 Front and Back Panels
Table 3SRA 1600 Front Panel Features
Front Panel FeatureDescription
Console PortRJ-45 port, provides access to console messages with serial connec-
tion (115200 Baud). Provides access to command line interface (for
future use).
USB PortsProvides access to USB interface (for future use).
Reset ButtonProvides access to SafeMode.
Power LEDIndicates the SRA 1600 is powered on.
Test LEDIndicates the SRA 1600 is in test mode.
Alarm LEDIndicates a critical error or failure.
X1Provides access to the X1 interface and to SRA resources.
X0Default management port. Provides connectivity between the SRA
1600 and your gateway.
Table 4SRA 1600 Back Panel Features
Back Panel FeatureDescription
Exhaust fanProvides optimal cooling for the SRA 1600 appliance.
Power plugProvides power connection using supplied power cord.
Power switchPowers the SRA 1600 on and off.
SRA Overview | 15
SRA 4200 Front and Back Panels Overview
Figure 3SRA 4200 Front and Back Panels
Table 5SRA 4200 Front Panel Features
Front Panel FeatureDescription
Console PortRJ-45 port, provides access to console messages with serial connec-
tion (115200 Baud). Provides access to command line interface (for
future use).
USB PortsProvides access to USB interface (for future use).
Reset ButtonProvides access to SafeMode.
Power LEDIndicates the SRA 4200 is powered on.
Test LEDIndicates the SRA 4200 is in test mode.
Alarm LEDIndicates a critical error or failure.
X3Provides access to the X3 interface and to SRA resources.
X2Provides access to the X2 interface and to SRA resources.
X1Provides access to the X1 interface and to SRA resources.
X0Default management port. Provides connectivity between the SRA
4200 and your gateway.
Table 6SRA 4200 Back Panel Features
Back Panel FeatureDescription
Exhaust fansProvides optimal cooling for the SRA 4200 appliance.
Power plugProvides power connection using supplied power cord.
Power switchPowers the SRA 4200 on and off.
16 | SRA 6.0 Administrator’s Guide
SRA 1200 Front Panel Overview
Figure 4SRA 1200 Front Panel
Table 7SRA 1200 Front Panel Features
Front Panel FeatureDescription
Console PortRJ-45 port, provides access to console messages with serial connec-
USB PortsProvides access to USB interface (for future use).
Reset ButtonProvides access to SafeMode.
Power LEDIndicates the SRA 1200 is powered on.
Test LEDIndicates the SRA 1200 is in test mode.
Alarm LEDIndicates a critical error or failure.
X1Provides access to the X1 interface and to SRA resources.
X0Default management port. Provides connectivity between the SRA
tion (115200 Baud). Provides access to command line interface (for
future use).
1200 and your gateway.
SRA Overview | 17
Concepts for Dell SonicWALL SRA
This section provides an overview of the following key concepts, with which the administrator
should be familiar when using the SRA appliance and Web-based management interface:
•“Encryption Overview” section on page 18
•“SSL Handshake Procedure” section on page 19
•“IPv6 Support Overview” section on page 19
•“Browser Requirements for the SRA Administrator” section on page 22
•“Browser Requirements for the SRA End User” section on page 22
•“Portals Overview” section on page 23
•“Domains Overview” section on page 23
•“Application Offloading and HTTP(S) Bookmarks Overview” section on page 23
•“Cross Domain Single Sign-On” section on page 28
•“ActiveSync Authentication” section on page 28
•“Network Resources Overview” section on page 33
•“SNMP Overview” section on page 39
•“DNS Overview” section on page 39
•“Network Routes Overview” section on page 39
•“NetExtender Overview” section on page 39
•“Two-Factor Authentication Overview” section on page 43
•“One Time Password Overview” section on page 46
•“End Point Control Overview” section on page 48
•“Secure Virtual Assist Overview” section on page 49
•“Web Application Firewall Overview” section on page 60
Encryption Overview
Encryption enables users to encode data, making it secure from unauthorized viewers.
Encryption provides a private and secure method of communication over the Internet.
A special type of encryption known as Public Key Encryption (PKE) comprises a public and a
private key for encrypting and decrypting data. With public key encryption, an entity, such as a
secure Web site, generates a public and a private key . A secure W eb server sends a public key
to a user who accesses the Web site. The public key allows the user’s Web browser to decrypt
data that had been encrypted with the private key. The user’s Web browser can also
transparently encrypt data using the public key and this data can only be decrypted by the
secure Web server’s private key.
Public key encryption allows the user to confirm the identity of the Web site through an SSL
certificate. After a user contacts the SRA appliance, the appliance sends the user its own
encryption information, including an SSL certificate with a public encryption key.
18 | SRA 6.0 Administrator’s Guide
SSL Handshake Procedure
The following procedure is an example of the standard steps required to establish an SSL
session between a user and an SRA gateway using the SRA Web-based management
interface:
Step 1When a user attempts to connect to the SRA appliance, the user’s Web browser sends
information about the types of encryption supported by the browser to the appliance.
Step 2The appliance sends the user its own encryption information, including an SSL certificate with
a public encryption key.
Step 3The Web browser validates the SSL certificate with the Certificate Authority identified by the
SSL certificate.
Step 4The Web browser generates a pre-master encryption key, encrypts the pre-master key using
the public key included with the SSL certificate and sends the encrypted pre-master key to the
SRA gateway.
Step 5The SRA gateway uses the pre-master key to create a master key and sends the new master
key to the user’s Web browser.
Step 6The browser and the SRA gateway use the master key and the agreed upon encryption
algorithm to establish an SSL connection. From this point on, the user and the SRA gateway
will encrypt and decrypt data using the same encryption key. This is called symmetric
encryption.
Step 7Once the SSL connection is established, the SRA gateway will encrypt and send the Web
browser the SRA gateway login page.
Step 8The user submits his user name, password, and domain name.
Step 9If the user’s domain name requires authentication through a RADIUS, LDAP, NT Domain, or
Active Directory Server, the SRA gateway forwards the user’s information to the appropriate
server for authentication.
Step 10 Once authenticated, the user can access the SRA portal.
IPv6 Support Overview
Internet Protocol version 6 (IPv6) is a replacement for IPv4 that is becoming more frequently
used on networked devices. IPv6 is a suite of protocols and standards developed by the
Internet Engineering Task Force (IETF) that provides a larger address space than IPv4,
additional functionality and security, and resolves IPv4 design issues. You can use IPv6
without affecting IPv4 communications.
IPv6 supports stateful address configuration, which is used with a DHCPv6 server, and
stateless address configuration, where hosts on a link automatically configure themselves with
IPv6 addresses for the link, called link-local addresses.
In IPv6, source and destination addresses are 128 bits (16 bytes) in length. For reference, the
32-bit IPv4 address is represented in dotted-decimal format, divided by periods along 8-bit
boundaries. The 128-bit IPv6 address is divided by colons along 16-bit boundaries, where each
16-bit block is represented as a 4-digit hexadecimal number . This is called colon-hexadecimal.
The IPv6 address, 2008:0AB1:0000:1E2A:0123:0045:EE37:C9B4 can be simplified by
removing the leading zeros within each 16-bit block, as long as each block has at least one
digit. When suppressing leading zeros, the address representation becomes:
2008:AB1:0:1E2A:123:45:EE37:C9B4
SRA Overview | 19
When addresses contain contiguous sequences of 16-bit blocks set to zeros, the sequence can
be compressed to ::, a double-colon. For example, the link-local address of
2008:0:0:0:B67:89:ABCD:1234 can be compressed to 2008::B67:89:ABCD:1234. The
multicast address 2008:0:0:0:0:0:0:2 can be compressed to 2008::2.
The IPv6 prefix is the part of the address that indicates the bits of the subnet prefix. Prefixes
for IPv6 subnets, routes, and address ranges are written as address/prefix-length, or CIDR
notation. For example, 2008:AA::/48 and 2007:BB:0:89AB::/64 are IPv6 address prefixes.
SonicOS SSL VPN supports IPv6 in the following areas:
Services
•FTP Bookmark – Define a FTP bookmark using an IPv6 address.
•Telnet Bookmark – Define a Telnet bookmark using an IPv6 address.
•SSHv1 / SSHv2 Bookmark – Define an SSHv1 or SSHv2 bookmark using an IPv6 address.
•Reverse proxy for HTTP/HTTPS Bookmark – Define an HTTP or HTTPS bookmark using
an IPv6 address.
•Citrix Bookmark – Define a Citrix bookmark using an IPv6 address.
•RDP Bookmark - Define an RDP bookmark using an IPv6 address.
•VNC Bookmark - Define a VNC bookmark using an IPv6 address.
Note
IPv6 is not supported for File Shares (CIFS).
Settings
•Interface Settings – Define an IPv6 address for the interface. The link-local address is
displayed in a tooltip on Interfaces page.
•Route Settings – Define a static route with IPv6 destination network and gateway.
•Network Object – Define the network object using IPv6. An IPv6 address and IPv6 network
can be attached to this network object.
20 | SRA 6.0 Administrator’s Guide
NetExtender
When a client connects to NetExtender, it can get an IPv6 address from the SRA appliance if
the client machine supports IPv6 and an IPv6 address pool is configured on the SRA.
NetExtender supports IPv6 client connections from Windows systems running Vista or newer,
and from Linux clients.
Secure Virtual Assist
Users and Technicians can request and provide support when using IPv6 addresses.
Rules
•Policy rule – User or Group Policies. Three IPv6 options in the Apply Policy To drop-down
list:
–
IPv6 Address
–
IPv6 Address Range
–
All IPv6 Address
•Login rule – Use IPv6 for address fields:
–
Define Login From Defined Addresses using IPv6
–
Two IPv6 options in the Source Address drop-down list: IPv6 Address / IPv6 Network
Virtual Hosts
An administrator can assign an IPv6 address to a virtual host, and can use this address to
access the virtual host.
SRA Overview | 21
Application Offloading
SSL VPN
Management
Interface
Minimum Browser/Version
Requirements
2222222222
1616161616
8
89
Browser
Windows XP
Windows Vista
Windows 7Linux
MacOS X
An administrator can assign an IPv6 address to an application server used for application
offloading, and can use this address to access the server.
Browser Requirements for the SRA Administrator
The following Web browsers are supported for the SRA Web-based management interface and
the user portal, Virtua l O ff i c e . Java is only required for various aspects of the SRA Virtual
Office, not the management interface.
•Internet Explorer 8.0 or newer
•Firefox 16.0 or newer
•Chrome 22.0 or newer
The following table provides specific browser requirements.
Browser Requirements for the SRA End User
To configure SRA appliance using the Web-based management interface, an administrator
must use a Web browser with Java, JavaScript, ActiveX, cookies, popups, and SSLv3 or TLS
1.0 enabled.
The following is a list of Web browser and operating system support for va rious SRA pro tocols
including NetExtender and various Application Proxy elements. Minimum browser version
requirements are shown for Windows, Windows Vista, Windows 7, Linux, and MacOS.
SSL VPN
User
Interface
Minimum Browser/Version
Requirements
Browser
Windows XP
Windows Vista
8
2222222222
Windows 7Linux
89
161616
MacOS X
5
1616
22 | SRA 6.0 Administrator’s Guide
Portals Overview
The SRA appliance provides a mechanism called Virtual Office, which is a Web-based portal
interface that provides clients with easy access to internal resources in your organization.
Components such as NetExtender, Secure Virtual Assist, and bookmarks to file shares and
other network resources are presented to users through the Virtual Office portal. For
organizations with multiple user types, the SRA appliance allows for multiple customized
portals, each with its own set of shared resource bookmarks. Portals also allow for individual
domain and security certificates on a per-portal basis. The components in a portal are
customized when adding a portal.
File Shares
File shares provide remote users with a secure Web interface to Microsoft File Shares using
the CIFS (Common Internet File System) or SMB (Server Message Block) protocols. Using
a Web interface similar in style to Microsoft’ s familiar Network Neighborhood or My Network
Places, File Shares allow users with appropriate permissions to browse network shares,
rename, delete, retrieve, and upload files, and to create bookmarks for later recall. File
shares can be configured to allow restricted server path access.
Custom Portals
SRA appliances let you configure multiple portals, each with its own title, banner, login
message, logo and set of available resources. Each portal also enables you to set individual
Virtual Hosts/Domain Names to create a unique default portal URL. When a user logs into
a portal, he or she sees a set of pre-configured links and bookmarks that are specific to that
portal. You can configure whether or not NetExtender is displayed on a V irtual Of fice port al,
and if you want NetExtender to automatically launch when users log in to the portal. The
administrator configures which elements each portal displays through the Portal Settings
window. For information on configuring portals, refer to the “Portals > Portals” section on
page 129.
Domains Overview
A domain in the SRA environment is a mechanism that enables authentication of users
attempting to access the network being serviced by the SRA appliance. Domain types include
the SRA internal LocalDomain, and the external platforms Microsoft Active Directory, NT
Auth ent ica tio n, L DAP, and RAD IUS . Often, only one domain will suffice to provide authentication
to your organization, although a larger organization may require distributed domains to handle
multiple nodes or collections of users attempting to access applications through the portal. For
information about configuring domains, refer to the “Portals > Domains” section on page 148.
Application Offloading and HTTP(S) Bookmarks Overview
SRA appliances use HTTP(S) bookmarks and application offloading to provide access to Webbased applications running on servers within the intranet. This includes Sharepoint 2007 and
the enhanced versions of commonly-used Web mail interfaces, such as Microsoft OWA
Premium and Domino Web Access 8.0.1, 8.5.1, and 8.5.2. Sharepoint 2010 is supported with
application offloading, but not with HTTP(S) bookmarks.
SRA Overview | 23
Both application offloading and HTTP(S) bookmarks use an HTTP(S) reverse proxy . A rever se
proxy is a proxy server that is deployed between a remote user outside an intranet and a target
Web server within the intranet. The reverse proxy intercepts and forwards packet s that originate
from outside the intranet. An HTTP(S) reverse proxy specifically intercepts HTTP(S) requests
and responses.
Application Offloading provides secure access to both internal and publicly hosted Web
applications. An application offloading host is created as a special-purpose portal with an
associated virtual host acting as a proxy for the backend Web application.
Unlike HTTP(S) bookmarks, access to offloaded applications is not limited to remote users. The
administrator can enforce strong authentication and access policies for specific users or
groups. For instance, in an organization certain guest users may need Two-factor or Client
Certificate authentication to access Outlook Web Access (OWA), but are not allowed to access
OWA public folders. If authentication is enabled, multiple layers of advanced authentication
features such as One Time Password, Two-factor Authentication, Client Certificate
Authentication and Single Sign-On can be applied on top of each other for the offloaded host.
The offloaded application portal must be configured as a virtual host with a suitable SRA
domain. It is possible to disable authentication and access policy enforcement for such an
offloaded host.
Web transactions can be centrally monitored by viewing the logs. In addition, Web Application
Firewall can protect offloaded application hosts from any unexpected intrusion, such as Crosssite scripting or SQL Injection.
Access to offloaded Web applications happens seamlessly as URLs in the proxied p age are not
rewritten in the manner used by HTTP or HTTPS bookmarks.
For configuration information, see the “Portals > Application Offloading” section on page 142
and the “Adding or Editing User Bookmarks” section on page 302.
Benefits of HTTP(S) Bookmarks
By using HTTP(S) bookmarks, users can access the full-featured versions of Sharepoint 2007,
Microsoft OWA Premium, and Domino Web Access 8.0.1, 8.5.1, and 8.5.2 W eb mail interfaces.
These interfaces are easier to use and provide more enhanced features than their basic
counterparts.
Benefits of Application Offloading
An offloaded Web application has the following advantages over configuring the Web
application as an HTTP(S) bookmark in SRA:
•No URL rewriting is necessary, thereby improving throughput significantly.
•The functionality of the original Web application is retained almost completely, while an
HTTP(S) bookmark is a best-effort solution.
•Application offloading extends SRA security features to publicly hosted Web sites.
Application offloading can be used in any of the following scenarios:
•To function as an SSL offloader and add HTTPS support to the offloaded Web application,
using the integrated SSL accelerator hardware of the SRA appliance.
•In conjunction with the Web Application Firewall subscription service to provide the
offloaded Web application continuous protection from malicious Web attacks.
•To add strong or stacked authentication to the offloaded Web application, including Two-
factor authentication, One Time Passwords and Client Certificate authentication.
•To control granular access to the offloaded Web application using global, group or user
based access policies.
24 | SRA 6.0 Administrator’s Guide
•To support Web applications not currently supported by HTTP/HTTPS bookmarks.
Application Offloading does not require URL rewriting, thereby delivering complete
application functionality without compromising throughput.
•To authenticate ActiveSync Application Offloading technology, which delivers Web
applications using Virtual Hosting and Reverse Proxy. ActiveSync authentication does not
require URL rewriting in order to deliver the Web applications seamlessly. As an example,
the ActiveSync protocol is used by a mobile phone’s email client to synchronize with an
Exchange server, as explained in “ActiveSync Authentication” on page 28.
Supported Platforms
Appliance Platforms
On SRA 6.0, Application Offloading and HTTP(S) bookmarks are supported on the following
SRA appliances:
•SRA 4600
•SRA 4200
•SRA 1600
•SRA 1200
•SRA Virtual Appliance
HTTP Versions
HTTP(S) bookmarks and application offloading portals support both HTTP/1.0 and HTTP/1.1.
Certain performance optimization features, such as caching, compression, SSL hardware
acceleration, HTTP connection persistence, TCP connection multiplexing and transfer-chunk
encoding for proxies are automatically enabled depending on the usage.
Applications
In SRA 6.0, Sharepoint 2010 is supported with application offloading, but not with HTTP(S)
bookmarks. The following features have been tested and verified as working well on the
indicated browsers:
Internet Explorer 8 and 9
Firefox 16.0+
Chrome 22.0+
The following Web applications have been tested and verified to work with HTTP(S) bookmarks
and as offloaded applications:
•Microsoft Outlook Web Access 2010
Microsoft Outlook Web Access 2007
Microsoft Outlook Web Access 2003
SRA Overview | 25
Note
In SRA 6.0, Application Offloading supports authentication for ActiveSync. ActiveSync is a
protocol used by a mobile phone’s email client to synchronize with an Exchange server. The
Administrator can create an offloading portal and set the application server host to the
backend Exchange server. Then, a user can use the new virtual host name in a mobile
phone’s email client, and synchronize with the backend Exchange server through the SRA
appliance. Before SRA 6.0, users had to disable authentication for ActiveSync offloading
portals, because ActiveSync requests are different from requests sent from the browser.
Outlook Web Access is supported on the SRA 4600/4200/1600/1200 and SRA Virtual
Appliance platforms.
•Windows Sharepoint 2007
Windows Sharepoint Services 3.0
Windows Sharepoint Services 2.0
The integrated client features of Sharepoint are not supported.
•Lotus Domino Web Access 8.0.1, 8.5.1, and 8.5.2
Domino Web Access is supported on the SRA 4600/4200/1600/1200 and SRA Virtual
Appliance platforms.
•Novell Groupwise Web Access 7.0
•ActiveSync with Microsoft Exchange 2010
ActiveSync with Microsoft Exchange 2007
ActiveSync with Microsoft Exchange 2003
Exchange ActiveSync is supported on the following:
•Apple iPhone
•Apple iPad
•Android 2.3.x (Gingerbread), 4.0.x (ICS) and 4.1 (Jelly Bean) based phones
•Windows Mobile 6.5 based phones
•Windows Mobile 6.0 based phones
Authentication Schemes
The following authentication schemes are supported for use with application offloading and
HTTP(S) bookmarks:
•Basic – Collects credentials in the form of a username and password.
•NTLM (Microsoft NT LAN Manager) – Provides automatic authentication between Active
Directory aware applications.
•Forms-based authentication – Uses a Web form to collect credentials.
Software Prerequisites
The following end-user requirements must be met in order to access the complete set of
application offloading and HTTP(S) bookmarks features:
•Internet Explorer 8.0 or newer
•Windows 7, Windows 2000, Windows XP, or Windows Server 2003 or later
26 | SRA 6.0 Administrator’s Guide
Supported Applications
When using application offloading or HTTP(S) bookmarks to access applications for Webbased clients, full feature sets are accessible to users. SRA 6.0, application offloading and
HTTP(S) bookmarks provide enhanced application support for the following software
applications:
•Sharepoint Server 2007
•Sharepoint Server 2010
•Microsoft Outlook Web Access Premium
•Lotus Domino Web Access 8.0.1, 8.5.1, and 8.5.2
Note• The maximum number of users supported is limited by the number of applications being
accessed and the volume of application traffic being sent.
•Feature support varies based on your hardware and installation, see the respective
sections for more detailed information about specific application support.
Tip If you are using the correct Web browser and operating system, and a supported application
does not work, delete the browser session cookies, close and reopen all instances of your
browser, clear the browser cache, and then try again.
Supported Application Deployment Considerations
Be aware of these installation and general feature caveats when using application offloading
and HTTP(S) bookmarks with the following software applications:
•Sharepoint
–
For features that rely on Windows Sharepoint Services-compatible client programs,
SRA 6.0 application offloading and HTTP(S) bookmarks do not support client
integration capabilities on Internet Explorer.
–
Only forms-based authentication and basic authentication schemes are supported.
–
Single Sign-On is supported only for basic authentication.
–
Sharepoint 2010 is supported with application offloading, but not with HTTP(S)
bookmarks.
•Microsoft OWA
–
S/MIME support and bi-directional layout support for Arabic and Hebrew in Microsoft
OWA Premium are only available using Internet Explorer 8 and later . Gzip compression
supported by Microsoft OWA Premium is not supported through the reverse proxy.
Application Offloading should support any application using HTTP/HTTPS. SRA has limited
support for applications using Web services and no support for non-HTTP protocols wrapped
within HTTP.
The application should not contain hard-coded self-referencing URLs. If these are present, the
Application Offloading proxy must rewrite the URLs. Since Web site development does not
usually conform to HTML standards, the proxy can only do a best-effort translation when
rewriting these URLs. Specifying hard-coded, self-referencing URLs is not recommended when
developing a Web site because content developers must modify the Web pages whenever the
hosting server is moved to a different IP or hostname.
SRA Overview | 27
For example, if the backend application has a hard-coded IP address and scheme within URLs
as follows, Application Offloading must rewrite the URL.
<a href="http://1.1.1.1/doAction.cgi?test=foo
This can be done by enabling the Enable URL Rewriting for self-referenced URLs setting for
the Application Offloading Portal, but all the URLs may not be rewritten, depending on how the
Web application has been developed. (This limitation is usually the same for other WAF/SRA
vendors employing reverse proxy mode.)
Cross Domain Single Sign-On
External Website Bookmarks can be created for application offloading portals to achieve a
single point of access for users. This allows users to automatically log into application
offloading portals after logging into the main portal.
To use Cross Domain Single Sign-on (SSO), perform the following steps:
Step 1Create two or more portals with the same shared domain (from Virtual Host Domain name) and
that need authentication. One portal should be a regular portal. These portals are also in the
same SRA appliance’s domain so that a user can log in to both of them with the same
credentials. “Adding Portals” on page 131 explains how to create a portal.
Step 2Log into the portal and create a bookmark, as explained in “Adding or Editing User Bookmarks”
on page 302.
">
Step 3Set the service to External Web Site, as explained in “External Web Site” on page 309.
Step 4Enable Automatically log in for the bookmark, which enables Cross Domain SSO for this
bookmark.
Step 5Specify a Host, which is a portal with the same shared domain name.
Step 6Save the bookmark and launch it. The new portal is logged in automatically without any
credential.
The shared domain names don’t need to be identical; a sub-domain also works. For example,
one portal is a regular portal whose virtual host domain name is “www.example.com” and its
shared domain name is “.example.com”. The other portal’s virtual host domain name is
“intranet.eng.example.com” and the shared domain name is “.eng.example.com”. If a
bookmark to xyz.eng.example.com is created in the www.example.com
SSO works because “.eng.example.com” is a sub-domain of “.example.com”.
ActiveSync Authentication
Applicat ion Offloading now supports authentication for ActiveSync.Application Offloading
technology delivers Web applications using Virtual Hosting and Reverse Proxy . Users still need
to authenticate with the SRA appliance before accessing the backend Web application.
However, the proxy avoids URL rewriting in order to deliver the Web applications seamlessly.
ActiveSync is a protocol used by a mobile phone’s email client to synchronize with an Exchange
server. The Administrator can create an of floading port al and set the application server host to
the backend Exchange server. Then, a user can use the new virtual host name in a mobile
phone’s email client, and synchronize with the backend Exchange server through the SRA
appliance. Before SRA 6.0, users had to disable authentication for ActiveSync offloading
portals, because ActiveSync requests are different from requests sent from the browser.
portal, Cross Domain
28 | SRA 6.0 Administrator’s Guide
ActiveSync is managed through the Portals > Offloading > Security Settings page:
To configure ActiveSync authentication, clear the Disable Authentication Controls check box
to display the authentication fields. Select the Enable ActiveSync authentication check box
and then type the default domain name. The default domain name will not be used when the
domain name is set in the email client’s setting.
ActiveSync Log Entries
The Log > View page is updated when a Web application is offloaded. Most mobile systems
(iPhone, Android, Windows Mobile, etc.) support ActiveSync. These log entries identify when
the client began to use ActiveSync through the offloading portal. The ActiveSync message
identifies the device ID (ActiveSync: Device Id is…) for an ActiveSync request unless a client
sets up the account and the request does not contain a device ID. The ActiveSync label is not
used in log entries for anonymous users who use ActiveSync.
Note
A user’s credential in the Exchange server must be the same as the one in the SRA. Many
authentication types are available for each domain in the SRA. If using the Local User
Database, make sure the user name and password is the same as the one for the Exchange
server. Fortunately , other authentication types like Active Dire ctory can share credentials for
both the Exchange server and SRA appliance. However , authentication using authentication
types that share credentials may take longer and the first ActiveSync request may time out.
Once authentication succeeds, a session is created and other requests won’t need to be
authenticated again.
Configuring a Portal to Check Email From an Android Device
The following example shows how to set up ActiveSync to check emails from an Android
device. Be sure to replace entries shown in the examples with entries for your environment, and
be careful to input the correct password. Otherwise, the account will be blocked.
SRA Overview | 29
Step 1In the SRA appliance, create an offloading portal with the name webmail.
Step 2Set the Scheme to Secure Web (HTTPS).
Step 3Set the Application Server Host to your Exchange server , for example webmail.example.com.
Step 4Set the virtual host name, for example, webmail.example.com. The virtual host name should be
resolved by the DNS server. Otherwise, modify the hosts file in the Android phone.
Step 5Select the Enable ActiveSync Authentication check box. Leave the default domain name
blank or input webmail.example.com.
30 | SRA 6.0 Administrator’s Guide
Loading...
+ 410 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.