Configure Web Application Proxy - Celestix E6600 Installation Manual

E series
Table of Contents

Advertisement

2. Finish – review the settings; click Next to configure.
The wizard is complete when the congratulations screen displays. Depending on the configuration to be
completed, this may take some time.
The base level setup for Remote Access options is now complete. Clients can now be configured to
access resources.

Configure Web Application Proxy

The wizard provides the steps to configure Web Application Proxy (WAP) settings for the Celestix Edge E
Series Appliance. Instructions cover the steps common to most deployments, but again, an individual
organization may require different or additional configuration.
For setup, the administrator needs access to the following resources:
• The external firewall (see
• The E Series appliance web UI
• Deployments that include the SSO Portal will require additional DNS records and firewall rules
General Information
provides necessary details to complete configuration.
General Information
The following deployment notes provide information to understand Web Application Proxy configuration.
Deployment Assumptions
Information presented in the E Series setup instructions is based on the following:
• The Web Application Proxy feature has been installed through the web UI.
• Deployment is a single proxy server.
• AD will be used for authentication and authorization through ADFS.
• Internal DNS entries have been configured for Web Application Proxy to resolve hostnames for
backend servers.
• Public DNS entries have been configured to resolve external URLs for each published application.
Firewall
rules have been configured to allow traffic for the following connectivity:
▪ To ADFS through port 443
▪ To AD
▪ To published applications as required
Requirement Checklist
The following items will be required to set up the proxy. Plan ahead so that items are available when
needed.
• ADFS – must be deployed on a separate server.
• ADFS administrator account – required to access ADFS for authentication.
• Publicly signed certificate – an SSL certificate is required; it is strongly recommended to use a
third-party certificate from a trusted vendor. The certificate subject is the same as the federation
service namespace.
• SSO portal address – optional configuration; if the portal is deployed, an FQDN will be needed to
assign to the SSO portal for end user access to hosted applications.
36
Firewall Ports
Reference)
E Series Installation Guide

Advertisement

Table of Contents
loading

Table of Contents