All Products
Search
Document Center

Secure Access Service Edge:Configure private access

Last Updated:Jun 04, 2026

Learn how to set up private access after activating the SASE platform. This guide covers IdP configuration, configuring private application resources, network connection, and zero trust policy creation.

Private access

Private access is a SaaS-based zero-trust network access (ZTNA) feature built on software-defined perimeter (SDP) technology. The SASE private access solution lets employees access cloud-based business resources while you maintain control over their access permissions, without exposing public IP addresses or modifying your corporate network architecture.

image

Procedure

Step 1: Configure an identity provider (IdP)

An identity provider (IdP) authenticates your employees. SASE supports both third-party and self-managed identity providers (IdPs), including LDAP, DingTalk, WeCom, Lark, IDaaS, and custom IdPs. If your business uses multiple IdPs, configure all of them so different teams use the SASE service with their preferred provider.

The following example uses a custom IdP.

  1. Log on to the SASE platform.

  2. In the left-side navigation pane, choose Identity Authentication > Identity Access.

  3. On the Identity synchronization tab, find Custom IdP, and click Actions in the Edit column. Configure the custom IdP by following the wizard. For more information, see Connect to a custom identity provider.

  4. On the User Group Management tab, click Create User Group.

  5. In the Create User Group panel, configure the Organizational Structure, Account Name, Email Address, Mobile Phone Number, and other information for the user group. Then, click OK. User Group Management.

Step 2: Configure a user group

A policy must target a user group. Create one if needed.

  1. In the left-side navigation pane, choose Identity Authentication > Identity Access.

  2. On the User Group Management tab, click Create User Group.

  3. In the Create User Group panel, configure the Organizational Structure, Account Name, Email Address, Mobile Phone Number, and other information for the user group. Then, click OK. User Group Management.

Step 3: Configure private application resources

Private applications are internal IT resources—such as applications, servers, or databases—that employees access from their work devices through the SASE client after passing identity and security policy checks. No public IP addresses are required for these LAN applications or resources.

  1. In the navigation pane on the left, choose Private Access > Application Management.

  2. On the Office Application page, in the Custom Tags section, click Add, enter a tag name, and then click OK.

    You can add up to 100 custom tags.

  3. Click Add Application and configure the application as follows.

    If your services use a DNS server to resolve your internal network segments, you can click Internal DNS Configuration. In the DNS Address dialog box, manually specify the Default DNS Service and Other DNS Services. The default DNS group (a DNS group can contain up to two DNS server IP addresses) is sent to the SASE client as the primary enterprise DNS. Employees can switch DNS groups on the client to meet specific access requirements.

    If you do not configure a DNS service, SASE uses Alibaba Cloud DNS by default for internal network resolution. If Alibaba Cloud DNS PrivateZone is configured, it is prioritized for resolving IP addresses or domain names.

    1. On the Manual Configuration tab, set the basic parameters as described in the following table.

      Parameter

      Description

      Example

      Application Name

      The name of the private application.

      The name must be 1 to 128 characters in length and can contain Chinese characters, letters, digits, hyphens (-), underscores (_), and periods (.).

      Attendance Management App

      Description

      A description of the private application.

      Attendance management portal for employees

      Tag

      A custom tag for the application, used to categorize, search for, and manage applications.

      OA_System

      Status

      The access status of the application. Valid values:

      • Enable: The application is available.

      • Disable: The application is unavailable.

      Enabled

    2. Click Next and set the application address information as described in the following table.

      Parameter

      Description

      Example

      Application Address

      The private access address. Supports IP addresses, CIDR blocks, domain names, and wildcard domain names. You can specify multiple addresses.

      10.10.XX.XX

      Port

      The port number or port range used by the application.

      80-200

      Protocol

      The protocol type of the application. Valid values: All Protocols, TCP, and UDP.

      All

    image.png

Step 4: Establish a network connection

Identify your deployment scenario to select the correct connection method.

Service deployment environment

Solution

Environment requirements

Enterprise services and resources are deployed on Alibaba Cloud

Use the network configuration feature to establish network connections between specified Alibaba Cloud VPC resources and SASE end users.

On the Network Configuration > Alibaba Cloud Services page, enable the network connection for the VPC where the target service server is located.

Requirements for office computers:

  • Windows (64-bit, 32-bit, .msi 64-bit, .msi 32-bit): Windows 7 or later

  • macOS: macOS 10.10 or later

  • Linux: Ubuntu 18.04 or later, UOS

Enterprise services and resources are deployed in a non-Alibaba Cloud environment, such as AWS or Tencent Cloud, and an Alibaba Cloud Virtual Border Router (VBR), Cloud Connect Network (CCN), or VPN Gateway is already used for network connectivity.

Use Alibaba Cloud network channels, such as Leased Lines, SAG, or IPsec-VPN, to allow SASE clients to access service resources in non-Alibaba Cloud environments.

On the Network Configuration > Non-Alibaba Cloud Services > Cloud Network Instance tab, configure the origin fetch VPC and enable the network connection.

Requirements for office computers:

  • Windows (64-bit, 32-bit, .msi 64-bit, .msi 32-bit): Windows 7 or later

  • macOS: macOS 10.10 or later

  • Linux: Ubuntu 18.04 or later, UOS

Enterprise services and resources are deployed in a non-Alibaba Cloud environment

SASE provides a connector feature that you can use to connect to your non-Alibaba Cloud network. This lets you use the SASE app to access services in the non-Alibaba Cloud environment.

This method does not depend on other network products for network access.

On the Network Configuration > Non-Alibaba Cloud Services > Connector List tab, manually add an SASE connector. Then, run commands to deploy the connector and ensure that the connector instance is enabled.

Requirements for office computers:

  • Windows (64-bit, 32-bit, .msi 64-bit, .msi 32-bit): Windows 7 or later

  • macOS: macOS 10.10 or later

  • Linux: Ubuntu 18.04 or later, UOS

Server requirements for deploying the connector:

  • Virtual machine or server configuration:

    • CPU: 4 cores

    • Memory: 8 GB

    • Disk: 40 GB

    • Operating system: CentOS 7 or later

  • Network configuration: The server must be able to access the Internet. If a firewall is configured, you must allow outbound traffic on ports 443 and 8000 for the server or virtual machine on which the connector is deployed.

  • Specification limit: 200 MB of traffic forwarding.

  • Port requirements: Ensure that ports 9000 to 9010 are not occupied.

The following example uses a non-Alibaba Cloud deployment.

  1. In the left-side navigation pane, choose Private Access > Network Settings.

  2. On the Network Settings page, click the Services Outside Alibaba Cloud tab.

  3. Add a connector and associate it with an application.

    1. On the Connectors tab, click Add Connector.

      You can add a maximum of five connectors.

    2. In the Add Connector panel, configure the parameters based on your business requirements. Then, click OK.

      Parameter

      Description

      Example

      Region

      The region of the connector. Select the region closest to your server for optimal performance.

      China (Beijing)

      Instance Name

      The name of the connector.

      private-access-connector-for-company-X

      Instance Switch

      Enables or disables the connector. SASE end users can access associated applications only when set to Enable.

      Important

      Disabling the Instance Switch will prevent end users from using the SASE App to access internal applications. Proceed with caution.

      Enabled

      image

  4. Install and deploy the connector.

    1. Click Actions in the Deploy column. In the Deploy panel, copy the full deployment command.

      image

    2. Log on to the target server or virtual machine as the root user and run the command.

Step 5: Create a zero trust policy

Zero trust policies help you control access to applications and resources for employees and partners. Creating a zero trust policy involves assigning resource permissions by linking user groups to business applications. A deny-all policy is in place by default—create allow policies to grant different user groups access to specific resources.

  1. In the left-side navigation pane, choose Private Access > Access Control.

  2. On the Zero Trust Policies tab, click Create Policy.

  3. In the Create Policy panel, configure the basic information as described in the following table, and then click OK.

    There is no limit on the number of zero trust policies you can create. You can create multiple policies to cover different access scenarios.

    Parameter

    Description

    Example

    Policy Name

    The name of the zero trust policy.

    The name must be 2 to 100 characters in length and can contain Chinese characters, letters, digits, hyphens (-), and underscores (_).

    Allow_Policy_for_Attendance_App

    Description

    A description of the zero trust policy.

    Allows all users to access the attendance management application.

    Priority

    The priority of the policy. Lower values take precedence (1 = highest). The maximum priority value for a new policy is the current number of zero trust policies plus one. For example, if you have 17 policies, the priority for a new policy can range from 1 to 18.

    Conflicting policies resolve by priority.

    1

    Action

    The access permission for the policy. Valid values:

    • Allow Access: Allows users or devices to access the specified application.

    • Access Denied: Denies users or devices access to the specified application.

    Allow

    Applicable User

    The user group this policy applies to. The zero trust policy takes effect on devices belonging to the specified user group. SASE allows or denies access requests that match the policy.

    Click Add. On the User Group tab, select a user group. If the existing user groups do not meet your needs, you can create a new one on the Custom User Group tab. User Group Management.

    All company employees

    Selected Applications

    The applications affected by the policy's Action.

    Click Add. On the Tag tab, select applications based on their tags. You can also select applications directly from the Application tab.

    Attendance Management App

    Security Baselines

    Select a security baseline template for your enterprise.

    -

    Policy Status

    Enables or disables the policy.

    Enabled

    image.png

Step 6: Verify the configuration

  1. Open your installed SASE client.

  2. Enter the enterprise verification ID and click OK.

    You can log on to the Secure Access Service Edge console. In the navigation pane on the left, on the Settings page, obtain the Enterprise Authentication Identifier.

  3. Log on by using the initial username and password that you received by email or text message.

  4. Click Connect to Private Network.

  5. Access the enterprise attendance management application.

    If you can access the application, the configuration is successful.