Discover related domains using a HAR file
Secure Private Access enables you to upload an HTTP Archive (HAR) file to automatically discover the domains accessed by an application. You can review the discovered domains and select the ones you want to add to the application’s related-domain configuration. This simplifies application onboarding by reducing the need to manually identify and configure related domains.
Previously, administrators had to know all of an application’s related domains in advance, or discover them reactively as users hit blocked URLs. Because every URL other than the ones configured is blocked by default, this reactive approach leads to a poor user experience. Secure Private Access had no way to identify the internal or embedded URLs within an application.
Example
Suppose you are configuring an application whose primary domain is example.com. While using the application, the browser also accesses several additional domains. For example:
-
api.example.com– Handles the application’s backend API calls. -
auth.example.com– Manages sign-in and authentication. -
cdn.example.com– Serves static content such as images, scripts, and stylesheets. -
login.microsoftonline.com– Provides third-party identity authentication. -
player.vimeo.com– Loads embedded video content.
Instead of identifying each of these domains manually:
- Capture a HAR file while using the application.
- Import the HAR file into Secure Private Access.
- Review the domains discovered by Secure Private Access. For example, the import might surface
api.example.com,auth.example.com, andcdn.example.comas required, along with domains such asplayer.vimeo.comthat you can choose to exclude. - Select the domains required by the application.
- Configure routing and resource locations as needed.
This provides a faster way to identify and configure the domains required for application connectivity.
Prerequisites
Ensure that you have captured a HAR file while accessing the Web or SaaS application. The HAR file must contain the network request information and must be 50 MB or smaller.
Import a HAR file
- In the Secure Private Access admin portal, open the Web or SaaS application you want to configure.
-
Go to App Connectivity and click Import HAR.
- Drag and drop the HAR file into the import window, or select the file from your device.
-
Secure Private Access analyzes the HAR file and displays the domains identified from the network requests.
- Review the discovered domains.
- Select the domains that you want to add to the application.
- Select Import.
The selected domains are added to the application’s Related Domains configuration.
Note:
Review the domains discovered before importing them. A HAR file can contain domains that are not required for the application’s connectivity.
Manage related domains
After importing the domains, you can manage them from the Related Domains table:
- Search for a domain – Use the search field to filter the table and quickly find a specific domain.
- Select domains – Select individual domains, or use the table header checkbox to select multiple domains. The selection can be used to perform actions on multiple domains at the same time.
- Edit domain configuration – Update the configuration of related domains, including the routing type, primary resource location, and secondary resource location.
- Bulk edit domains – Select multiple eligible domains and update their routing and resource-location settings at the same time. Bulk editing is available for applicable internal domains. External domains might not support all configuration options.
- Resource locations – When configuring a related domain, assign a primary and, where applicable, secondary resource location. Use these settings to define how Secure Private Access routes traffic for the related domain and which resource locations are used to provide connectivity.
Validation and file requirements
The HAR import feature validates the uploaded file before processing it.
- Only valid HAR files containing network request entries can be imported.
- The maximum supported file size is 50 MB.
- Domains are automatically extracted from the URLs in the HAR file.
- Duplicate domains are automatically removed.
- Domains are normalized before they are added to the related-domain configuration.