Native RDP Client Connection

GAccess allows you to connect to remote Windows servers using any standard RDP client — such as Remote Desktop Connection (Windows), Microsoft Remote Desktop (macOS), or FreeRDP (Linux). The GAccess Gateway acts as a transparent proxy: it authenticates you, retrieves the target credentials from the vault, and establishes the connection on your behalf. You never need to know the target password.

Gateway Address and Port

All native RDP connections go through the GAccess Gateway. Contact your administrator for the gateway hostname and port. The default port is 3389, but your organization may use a different one.

Username Format

Because the gateway proxies your connection to the target server, it needs to know both your GAccess identity and the destination. You provide all of this in the username field using the following format:

gaccess_email@target_username@target_hostname

Example:

john@acme.com@Administrator@10.0.1.50

Password

When prompted for a password, enter your GAccess account password. The gateway authenticates you, retrieves the target credential from the vault, and connects you to the Windows server transparently.

Local users with MFA: append | followed by your OTP to your password (e.g. MyPassword|482931).

Entra ID Federated users: use the temporary proxy token provided in the GAccess connection dialog instead of your password. See Federated Users below.

Option 1 — Pre-configured RDP File (Recommended)

The easiest way to connect is to download a pre-configured RDP file directly from the GAccess web interface. The file is already set up with the correct gateway address, username format, and session settings.

1. Open the GAccess web interface and navigate to the target server.
2. Click Connect and select the Native Connection tab.
3. Click Download Pre Configured RDP File.
4. Open the downloaded .rdp file — your RDP client will launch and connect automatically.
5. When prompted for a password, enter your GAccess password (or proxy token if you are a federated user).

The downloaded file is pre-filled with your username and the correct gateway address. You only need to provide the password.

Option 2 — Manual Connection (Remote Desktop Connection)

If you prefer to configure the connection manually:

1. Open Remote Desktop Connection (mstsc.exe on Windows, or Microsoft Remote Desktop on macOS).
2. Set the Computer field to the gateway address and port:

   gateway.yourcompany.com:3389

3. Click Show Options and set the Username to:

   john@acme.com@Administrator@10.0.1.50

4. Click Connect and enter your GAccess password when prompted.

Option 3 — FreeRDP (Linux)

Linux users can connect using FreeRDP. The GAccess connection dialog displays the exact command pre-filled with your details under the Native Connection tab:

xfreerdp /v:gateway.yourcompany.com:3389 \
  /u:"john@acme.com@Administrator@10.0.1.50" \
  /p:"YOUR_GACCESS_PASSWORD" \
  /cert:ignore

/cert:ignore suppresses the certificate prompt in FreeRDP. The connection is still encrypted — the gateway uses a trusted TLS certificate.

Federated Users — Proxy Token

If your organization uses Entra ID (or another identity provider), you cannot authenticate the gateway directly with your IdP credentials. Instead, GAccess generates a short-lived proxy token that you use in place of your password.

To get your proxy token:

1. Open the GAccess web interface and navigate to the target server.
2. Click Connect — the connection dialog will display your proxy token automatically.
3. Copy the token and use it as the password when your RDP client prompts for one.

Proxy tokens expire shortly after being generated. Request a new token for each connection attempt by reopening the connection dialog.

How Administrator Configuration Affects Your Connection

The capabilities available during your session depend on how your administrator has configured the target and your permissions:

• Clipboard — copy and paste between your machine and the remote desktop may be limited or disabled in one or both directions.
• File transfer — drive redirection and file sharing may be disabled by session policy.
• Session duration — a maximum session length may be enforced. The session will close automatically when the limit is reached.
• Session recording — your session may be recorded for audit and compliance purposes. A notice will appear at the start of the session if recording is active.

If you are unable to connect or a feature is unavailable, contact your administrator to verify your permissions and the target's session policy.