Quick Overview

The Apps section in zAccess allows administrators to define individual applications that endpoints can access. Each app entry is configured using either a web URL or an IP address and is paired with a designated gateway IP through which traffic should be routed. This is foundational to policy creation and enforcement.

How to Use This Feature in the UI

1. Navigate to the zAccess interface and select Policy Configuration > Apps.
2. Click on ADD APP.
3. Enter the application details:
   • App Name: A user-friendly label for identification.
   • IP Address or URL: The destination for which access is being configured.
   • Gateway IP: The local gateway through which traffic to this app should route.
4. Click Save to register the app configuration.
5. Repeat as necessary for other apps, or group them later using App Groups.

The App page allows configuration of the following supported types of applications with all necessary required inputs:

• Name
• Description
• Icon URL
• Type of app
  • Web Application
  • Native Application
  • Network Application
• URL of the app
• Auto-Connect
• Access Configuration of the app
  

Web Application

• Provide the hosted web application – URL and IP addresses of the hosted server.
• If the end-user needs to access the application through the zAccess client after login, enable the “Allow Auto-Connect” option to streamline access.

Native Application

• Select the operating system type (e.g., Windows, macOS, Linux)
• Provide the auto-launch path to enable the application to be opened directly via the zAccess client after successful login.
• Ensure that the application is installed on the machine where the zAccess client is running. The launch path should point to a valid executable or script that exists on the local system.

Network Application

• Configuration can be performed via either a web URL or a native application interface, as illustrated in the provided screenshot
• Define the CIDR notation for the target network segment.
• Applications within the specified subnet can be accessed through the zAccess gateway, provided that proper rules and policies are defined.

Concepts & Use Cases

• Access Control Granularity: Define access to specific applications or services rather than allowing unrestricted internet access.
• Gateway-Aware Routing: Direct application traffic through designated paths (gateways), optimizing performance or enforcing security boundaries.
• Application Whitelisting: Combine with policies and rulesets to implement app-specific allowlists.
• Compliance Control: Restrict access to only approved enterprise services, especially for remote or mobile users.

Troubleshooting & FAQs

• Why is my app not reachable?
  Ensure the gateway IP is correctly configured and reachable from the endpoint’s assigned subnet.
• Can I assign the same app to multiple gateways?
  Yes, but you’ll need to define separate entries for each app-gateway pair or group them accordingly for conditional routing.
• What if the app uses a dynamic IP?
  Use a domain name instead of an IP address to account for DNS-based resolution.
• Is there logging for app access?
  Yes, app access attempts can be tracked via endpoint sessions and event logs.
• Does the gateway need to host the application?
  No, the gateway acts as a route/path enforcement point, not a host for the application itself.