Private applications
Use the page to define the internal applications that users will be able to access remotely.
Defining a private application in the Private Access management portal links your internal application with the external addresses that will be used to access it remotely. A private application definition consists of the following elements.
| Property | Description | Required? |
|---|---|---|
| Name | The application name, used in private application policy rules. | Required |
| Description | An optional description for the application. | Optional |
| Site |
The application hosting site for the internal application. Remote traffic for this application that passes through your private applications policy is directed to the hosting site using the site's tunnel connections. When you save the application, the Service edge is displayed for the site. |
Required |
| Service edge |
The external address for the Private Access proxy that handles incoming traffic for this application hosting site from your remote users. This address is required as part of Cloud Security Gateway setup. |
N/A |
| External FQDN | The fully qualified domain name that remote users will use to access the internal application remotely. This FQDN should not be a publicly routable domain. | Required |
| Protocol | The protocol used by the application. Currently, HTTP/HTTPS are supported. | N/A |
| Port | The port used by the application. Enter a port number or range if the application uses non-standard ports. Enter a single port number, or a port range separated with a hyphen, for example: "8080-8090". | Optional |
| Internal address |
The internal IP address or domain used to access the application on your local network. This address must be accessible from the IPsec tunnel on your edge device that connects to the Private Access gateway. |
Required |