--- title: "Adding a Portal" slug: "adding-a-portal-v7-0" description: "Access protected network resources seamlessly with the Portal's web frontend, supporting up to 1,000 users through secure browser sessions." tags: ["Appliance Configuration", "Portal", "Appliance Functions"] updated: 2026-11-19T17:11:59Z published: 2026-11-19T17:11:59Z canonical: "support.appgate.com/adding-a-portal-v7-0" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.appgate.com/llms.txt > Use this file to discover all available pages before exploring further. # Adding a Portal The Portal hosts a web frontend that allows browser-based access for multiple users without requiring a standalone client. Users connect to protected network resources through a browser, using a client instance hosted on the Portal appliance. The Portal supports up to approximately 1,000 client instances, depending on available memory. When the Portal reaches capacity, it ends idle sessions to make room for new users. Active sessions are not affected. Each instance supports one user or browser session. Each client instance assigned to an authenticated user consumes one Portal user [license](/v1/docs/licenses-v7-0). --- ## Before adding a Portal Before adding a Portal, complete the following: - Decide how users will reach protected hosts through the Portal: - **Subdomain mappings (recommended):** Map a public subdomain alias to each internal app domain. Internal domains don’t need to be publicly resolvable. - **Published internal hostnames:** Publish the internal DNS names of protected hosts to external DNS. If a name isn’t suitable for publishing, create an alias and add it as a CNAME to its internal DNS record. - Deploy AppGate ZTNA and verify that full client users have the required access to protected hosts. - Determine which identity provider (IdP) you will use: - The [MFA at sign-in](/v1/docs/mfa-providers-v7-0#mfa-at-signin) feature works differently for Portal users. You may want to use a different IdP. - If you are using SAML authentication, you need a new or updated SAML IdP configuration with a different [Single Sign-on URL (ACS URL)](/v1/docs/saml-provider-v7-0#single-signon-url-acs-url). --- ## Configuring a Portal To configure a Portal, select the ***Portal*** checkbox on the ***Functions*** tab of the **Edit Appliance** page, then complete the following fields. ### Site Settings - ***Appliance Site***. Select the Site from the drop-down. ### User Access Settings - ***Client Profiles.*** Select **+Add** and use the ***Profile Name*** dropdown to add one or more client profiles for users to select at sign-in. [Create a new profile](/v1/docs/configure-client-profiles-v7-0) if you are using a new IdP, or if the `profileName` claim will be useful when assigning policies for Portal users. - ***Client Profiles from External Collectives.*** Select **+Add** and enter the URL of an external client profile to allow the Portal to be used with multiple Collectives. - ***Listening Ports.*** By default, HTTPS port 443 is open for incoming traffic. Select **+Add** to add ports to proxy. - ***HTTP Redirect.*** When selected, HTTP port 80 redirects to port 443. When cleared, the Portal does not respond on port 80. - ***Proxied Entitlement Certificates (PKCS #12).*** Select **+Add** to upload a PKCS #12 file and enter its password. This can be a wildcard certificate, multiple certificates, or a single certificate with SAN entries that cover all protected hosts accessed through the Portal. Select ***Verify Upstream*** to verify that all upstream servers present valid certificates matching their hostnames. - ***Subdomain Mappings***. Maps a short public subdomain alias to an internal app domain, so users can reach internal resources without publishing internal domains to external DNS. The Portal builds each alias by adding the subdomain to the front of the Portal hostname (`<subdomain>.<Portal hostname>`). For example, if the Portal hostname is `portal.example.com`, mapping `teamcity` to `teamcity.your-companys-domain` lets users go to `teamcity.portal.example.com`, and the Portal proxies traffic to the internal app domain. Select **+Add** to enter values in the following fields: - *Subdomain.* The leftmost DNS label of the public alias (for example, `teamcity`, which becomes `teamcity.<Portal hostname>`). Must be a valid DNS label: letters, digits, and hyphens only. Maximum is 63 characters. - *App Domain*. The fully-qualified internal app domain that traffic is proxied to (for example, `teamcity.your-companys-domain`). The domain does not need to be publicly resolvable, as it is resolved through the client’s VPN tunnel. - *Verify upstream certificate*. Select this checkbox to verify that all upstream servers present valid certificates matching their hostnames. ### HTTPS Settings - ***Portal Hostname.*** Enter the Portal public hostname. Use a fully qualified domain name (FQDN) that corresponds to the PKCS #12 file. - ***HTTPS Certificate (PKCS #12).*** Select **+Add** to upload a PKCS #12 file containing a CA-signed certificate for the Portal hostname, then enter its password. - ***Allowed Sources.*** By default, all incoming traffic is allowed. To restrict access, select **+Add** and enter the ***Address***, ***Netmask Length***, and ***Network Interface***. Only traffic from IP addresses matching at least one of these sources is allowed. - ***TLS Ciphers.*** Use the default ciphers unless your browsers have specific cipher requirements. Select **+Add** and use the dropdown to add a cipher. ### Customize Sign-in Page These fields are optional. - ***Logo.*** Upload a logo to display on the Portal sign-in page. The file must be under 100 KB and ideally 100 px by 200 px. - ***Background Image.*** Upload a background image for the Portal sign-in page. The file must be under 500 KB. - ***Text.*** Enter text to display on the Portal sign-in page. - ***Background Color.*** Set a background color for the Portal sign-in page. - ***Text Color.*** Set a color for the text entered in the ***Text*** field. - ***Preview.*** View a preview of your changes. - ***Automatic redirection after sign-in.*** When *Enabled* is selected, the website opens in the current tab instead of opening in a new tab with a confirmation prompt. > [!NOTE] > NOTE > > When automatic redirection is enabled, users do not see the AppGate ZTNA client tab. This may prevent them from resolving issues that require them to configure the system to stay connected. If this occurs, the user session closes and the user must reconnect. When you have finished configuring the Portal, move on to the [**Miscellaneous**](/v1/docs/adding-a-new-appliance-v7-0#miscellaneous) tab. After completing the configuration, [create a policy](/v1/docs/configuring-policies-v7-0) for Portal users and verify that you can sign in through the Portal and that the required app shortcuts appear. Use the `clientType` claim with the value `web`, the `profileName` claim, or both to assign the policy. For Portal best practices, see [System security - best practices](/v1/docs/system-security-best-practices-v7-0#22-portal-appliance1). For access issues, see [Gateway and Portal troubleshooting commands](/v1/docs/gateway-and-portal-troubleshooting-commands-v7-0). --- ## DNS requirements The Portal requires an FQDN for the Portal hostname. Users go to this hostname to sign in through a web client. The Portal also redirects users to this hostname if they navigate directly to the URL of a protected host. To terminate the HTTPS connection from the user, provide a PKCS #12 file containing a CA-signed certificate for the Portal hostname and the private key. ### Using subdomain mappings Each alias (`<subdomain>.<Portal hostname>`) must resolve to the Portal IP address in external DNS. The ***HTTPS Certificate (PKCS #12)*** under [HTTPS Settings](/v1/docs/adding-a-portal-v7-0#https-settings) must cover each alias, for example with a wildcard entry for `*.<Portal hostname>`. A wildcard entry doesn’t cover the Portal hostname itself, so the certificate needs both entries (for example, `portal.example.com` and `*.portal.example.com`). Entitlements use the internal app domain. The internal app domain must also resolve through the user’s tunnel. Make sure the DNS settings in the policy assigned to Portal users include the app domain. ### Using published internal hostnames The Portal does not perform URL rewriting. Instead, it uses a reverse web proxy based on NGINX, which terminates user application traffic and forwards it to protected hosts through AppGate ZTNA Gateways. Because the Portal does not rewrite URLs, the application hostnames used in entitlements must exactly match the hostnames used to connect to the Portal. Application hostnames entered in the browser, or configured in app shortcuts, must resolve to the Portal IP address. This requires you to publish the internal hostnames—but not the internal IP addresses—of protected hosts to external DNS. Every protected host accessed through the Portal requires an external DNS entry with a CNAME pointing to the Portal. This is only possible for resources you control. The Portal operates as a reverse proxy. It terminates HTTPS connections, decrypts them, and establishes new HTTPS connections to the protected hosts. The Portal supports multiple PKCS #12 files, each containing a CA-signed certificate and private key for a protected host. A wildcard certificate is an alternative to multiple certificates. Limit the scope of wildcard certificates, because a compromised wildcard certificate has significant security implications. --- ## Portal limitations The Portal has the following limitations: - Modern web browsers enforce security restrictions that prevent the Portal from supporting applications that use cross-origin requests. For example, a web app hosted on `https://app.company.com` that uses `https://api.company.com` as a REST backend is a cross-origin request and is not supported. All resources within a web app must be hosted on the same domain. Existing multi-domain web applications can be converted to single-domain applications using a reverse proxy such as NGINX. [Contact AppGate support](/v1/docs/contact-support) for more information. - Most SaaS applications cannot be accessed through the Portal because you do not control their DNS entries and cannot redirect the URL to the Portal. - The Portal requires WebSocket connections to maintain ongoing activity and deliver user notifications. To support this, the Portal injects a JavaScript file named `clientless-8c0fff68d47c43fa90127442303db814.js` into webpages. This file initiates WebSocket connections to the endpoint `/banner-16872eb861894a7e9e787f6355e95d3b`. In some cases, the injected JavaScript may conflict with Content Security Policy (CSP) headers, or notification rendering may conflict with existing page elements. [Contact AppGate support](/v1/docs/contact-support) if this occurs. - The Portal appliance does not support integrated high availability (HA), but you can place multiple Portals behind a load balancer. - Only one Portal appliance can be deployed per host, because the DNS entry must point to a single Portal appliance. - The Portal has limited built-in denial of service protection. Use appropriate external protection. - Internal application hostnames must be suitable for publishing through external DNS, unless you are using subdomain mappings or client-side host files. - Only HTTPS applications are supported. RDP over HTTPS is supported. - Web applications must support HTTP/1.1. AppGate ZTNA uses `proxy_pass`, which does not support HTTP/2. - Web applications with NTLM authentication are not supported. - The Portal supports a maximum of 1,000 users. The Portal keeps active sessions alive. If all client instances are in use when a new user signs in, the Portal ends idle sessions, starting with the oldest, to free capacity. - With subdomain mappings, the Portal doesn’t rewrite page content. An app might not work, or might expose its internal app domain, if it sets cookies for the internal domain, includes absolute URLs that use the internal domain, or redirects to `http://` or a non-default port. - The Portal connects to the internal app on the same port the user connected to on the Portal. For example, if users connect on port 443, the app must accept connections on port 443.