Oplon Client

Oplon Client was created to meet Oplon’s needs for sharing network folders, accessing Layer 4 services in PAM/ZTNA mode, performing posture checks and other operations that require a local client. Since Oplon Secure Access is plugin-free and agentless by design (no VPN, no persistent plugins), this client represents Oplon’s first official approach for Windows, Linux and macOS, providing a secure and verified way to connect local resources and remote services.

Features: Shared Folders and Trusted Connections

• Shared Folders: allows mounting shared network resources directly into the local file system in a secure way using Secure Access verification.
• Trusted Connections: exposes backend services via a local endpoint (localhost:random-or-custom-port) that the user can use instead of the real backend address.

Shared Folders: usage and behavior

• Usage: from the Secure Access interface, select the desired shared folder and click “Mount”.
• Behavior: the browser calls the local client; after the secret is verified the client mounts a volume in the local file system (e.g. as a drive on Windows, or a mount point on Linux/macOS).

Operational flow for Shared Folders:

1. Start the Oplon Client application on your system (Windows/Linux/macOS).

2. In the Oplon Secure Access web console, the left launcher will show an icon for Shared Folders with the list of available folders.

3. Select the desired folder and click “Mount”.

   

4. The browser will call the local Oplon client: the app will display a temporary secret.

   

5. Copy the secret from the local app and paste it into the Secure Access screen in the browser for verification.

   

6. After the token is verified the connection is established and the volume is mounted in the local file system.

   

• Note: the mount can be temporary or persistent depending on Oplon policy and user permissions.

Trusted Connections: usage and behavior

• Usage: from the Secure Access console select the desired service and click “Connect”.
• Behavior: after the browser calls the local app and the secret is verified, the client provides a local endpoint (e.g. http://localhost:PORT ) where PORT is a random or custom-configured port. Local applications or the browser can use this endpoint to communicate with the remote service as if it were local.

Operational flow for Trusted Connections:

1. Start the Oplon Client application on your system (Windows/Linux/macOS).

2. In the Oplon Secure Access web console, the left launcher will show an icon for Trusted Connections with the list of available services.

3. Select the desired service and click “Connect”.

   

4. The browser will call the local Oplon client: the app will display a temporary secret.

5. Copy the secret from the local app and paste it into the Secure Access screen in the browser for verification.

   

6. After the token is verified the connection is established: the client provides a local endpoint (http://localhost:PORT ) usable instead of the real backend address.

   

Viewing logs

To diagnose issues or provide information to support, Oplon Client allows easy access to the application’s log files.

Quick steps:

1. Start Oplon Client on your system.
2. Click the “Info” button at the bottom-left of the app window.
3. The “Info” window shows the path to the folder that contains the app logs.
4. Copy the path and paste it into a file manager to open the folder, or use the “Open folder” button if available.
5. Inspect the log files (.log, .txt) for the required information.