Plain VPN

What Is an SSL VPN? Browser Portals vs. Client Tunnels

简体中文

Your IT team sends you a remote-access link. Some coworkers finish their work in the browser, while others launch a VPN app. Both setups may be called an SSL VPN. Start by identifying the resource you need and the app you’ll use to reach it.

About 3 min read

Start with the resource you need

A browser portal often presents a list of authorized internal websites or apps after sign-in. The gateway provides access to the selected resource under the organization’s policy and the product’s capabilities. A client tunnel sends traffic according to the assigned VPN profile and can support approved desktop applications as well.

“SSL VPN” is a product term with a long history. Consult the documentation for your organization’s deployment to learn which TLS versions, devices, and connection modes it supports. Vendors can change or retire a mode between versions.

Match the connection to the task

TaskWhat to confirm
Open an expense page listed in the portalSign in at the official entry point and make sure the portal lists that application
Use a desktop tool to access an internal resourceAsk whether it requires a VPN client or device certificate and whether that tool is approved
Sign in successfully but see an empty app listCheck the account role and device requirements, then ask whether IT has assigned the app

One organization can offer both a portal and a tunnel. The right choice depends on the work and your access policy. Use the normal business resource or test page IT provides to confirm the setup.

Find the point where access stops

  1. 01 · BrowserSign in at the address IT supplied
  2. 02 · GatewayConfirm identity under the access policy
  3. 03 · Authorized appOpen a resource assigned to you
A typical browser portal session

Get the gateway address from a trusted channel and verify the domain. Pause if the browser displays a certificate warning. After authentication, check whether the portal lists the target app. If the app appears but fails to open, note whether you land back at sign-in, see an access-denied message, or hit a timeout. Those details point to different checks around session state, permissions, and connectivity.

If IT requires a client, use its supported app and profile. After connecting, test one resource supplied by IT. Record both the client status and whether the resource opened. A successful sign-in alone can’t show which stage blocked access.

Send IT a specific report

Include whether you used the portal or client, the application name, the failure stage, and the time. For example, “Portal MFA succeeded at 10:20 CST. The expense app was listed, but clicking it sent me back to the portal sign-in screen.” Redact internal addresses, employee IDs, and tokens from screenshots. Leave browser and device protections enabled.

Frequently asked questions

Does signing in to the portal connect my desktop apps?

Check your IT instructions. A portal typically grants access to the resources it publishes. A desktop app may need a separate client connection.

Can the company VPN work without changing my public IP?

Yes. Some deployments proxy only portal apps or route only corporate addresses. Test the authorized resource itself.

Sources