Desktop Access via Zero Trust
Most of your applications are now modern, responsive web apps. However, you still have some native Desktop applications. You need to be able to access them remotely, safely, simply. You need to be able to grant access to specific Desktops to specific users, but, they may not work for you. Your Desktop may run in a site without a public IP, or a configurable firewall allowing safe inbound access. Perhaps your house, perhaps a branch office.
In 10 minutes you can have 1-click remote access to that Desktop. With no configuration onsite, no change to the Desktop or the firewall.
Desktop Access Setup
Note: you can use a site-to-site VPN via IPSEC, or use the onsite Agilicus Agent Connector for each pool of servers. These instructions assume the latter.
Your Organisation lets you setup your identity providers, your DNS name (CNAME), and control your users.
SETUP IDENTITY PROVIDERS
You can enable Google, Apple, Mocrosoft as check box items. You may also wish to enable a specific Azure Active Directory
Also setup initial users and group membership.
CREATE CONNECTOR PER SITE
Each pool of servers needs a method to reach it. This can be a site-to-site VPN, or an on-site agent connector. Install a connector now, this may be on each remote-desktop server, on 1 of the servers that can reach the others, on a machine in the same network, a raspberry pi, whatever, it’s up to you.
CREATE DESKTOP RESOURCE
Each Desktop host will require a Desktop Resource to provide the coordinates. This will include a name, and hostname/IP. The Hostname/IP will be in the internal coordinates.
We must now assign ‘Owner’ permission to each user or group that should be able to connect. See “Resource Permissions” for more information.
DOWNLOAD RDP FILE
From https://profile.YOURDOMAIN, you may download a .rdp file for each Desktop. This will open in the client of your choice on the OS/Platform of your choice.
Detailed Desktop Creation
The ‘Desktops/New’ asks 3 questions:
- Connector. This you will have already setup, you need 1 per site (or more if you wish, e.g. 1 per host)
- Name. This will be the ‘name’ you assign permission to, it will show in the audit, the end-user will see it
- Hostname/IP. This is how you would address the Desktop within the (private) site.
Once you have completed these steps, as an Administrator you will be offered the opportunity to download an RDP file. This will open in your native Remote Desktop application (on all platforms). The Desktop will become available approximately 1-2 minutes after you apply the config.
You may now assign permissions (by group, or by user). Each user who has access will see, in https://profile.MYDOMAIN, an icon for the same RDP file. Each user’s .rdp file will be specifically signed with their access token, by default good for 1 week.
Return to Product Configuration
- Content Security Policy
- Identity & Authentication Methods
- Sign-In Theming
- Azure Active Directory
- Zero-Trust Desktop Access
- Zero-Trust SSH Access
- Command Line API Access
- Application Request Access
- Multi-Factor Authentication
- Synology Agent Connector Install
- OpenWRT Agent Connector Install
- Authentication Clients
- Authentication Rules
- Resource Permissions
- Legacy Active Directory