Web Apps let the SSL VPN act as the front end to your web servers on the Internet or Intranet. The SSL VPN service on the firewall receives the incoming web traffic through the SSL VPN web portal or CudaLaunch before forwarding it to the appropriate internal web-based service. The SSL VPN service handles authenticating users and secures all communication with SSL, allowing you to publish unsecured internal websites while still offering secure access to them.
Proxied Web Apps Using Templates
Frequently used proxied Web Apps, such as Outlook Web Access or SharePoint, are available as templates. Templates contain all the necessary configurations for the application and query the user for the required settings. By default, templates are configured to use the session username and password to log in.
Generic Proxied Web Apps
Generic proxied Web Apps are used either when a manual rewrite configuration is required, or when a template does not exist for the service. A simple setup creates a reverse proxy for the service. The data stream is not modified. For advanced configurations, you can configure additional paths, custom replacements, and headers. For services requiring authentication, a single sign-on configuration is possible.
For more information, see How to Configure a Generic Proxied Web App and Example - Use SSL VPN Web Apps for External File Share Links.
Tunneled Web Apps
A tunneled Web App uses an SSL tunnel established by CudaLaunch to connect to a web server behind the firewall. The user's browser connects to a localhost address (e.g.,. A direct connection to the resource located behind the SSL VPN is then established through the SSL tunnel. This type of Web App will only work as long as all links stay on the same destination host; it does not modify the data stream. If the destination site uses multiple domains, or sub-domains, use a proxied generic Web App instead. Tunnel Web Apps require CudaLaunch and an Advanced Remote Access subscription.
For more information, see How to Configure a Tunneled Web App.
Single Sign-On for Web Apps
Web services published through SSL VPN Web Apps often require the user to sign in. You can use session or user attributes as placeholders to configure single sign-on. Session attributes contain the username and password used to log into the SSL VPN service. If the credentials for the Web App differ, configure user attributes. When users access the Web App for the first time, they are prompted to fill in the username and password. Subsequent changes can be made in the SSL VPN web portal or via CudaLaunch.
For more information, see How to Configure Single Sign On for Proxied Web Apps.