Quick Start

Please follow the next steps to perform the required configuration to access a resource protected by Fyde Access Proxy.

1. Add new Fyde Access Proxy

  • Fyde Access Proxy is the software combo that contains Envoy Proxy and Fyde Proxy Orchestrator

  • Envoy Proxy listens to requests and proxies them to the correct destination

  • Fyde Proxy Orchestrator ensures that Envoy Proxy is configured with the correct requests and takes care of requests authorization and authentication

  • Fyde Proxy Orchestrator requires a valid token (Fyde Access Proxy enrollment link) that contains the necessary information to bootstrap and authorize the service

  • To add a Fyde Access Proxy, go to Fyde Enterprise Console, navigate to Access and then Proxies. Click the “+” icon in the top right.

  • This proxy will be used to test an access for the test resource, however this doesn’t prevent it from being used as a permanent proxy later on

    Control Screen

  • Add the following:

    • Proxy Name: Used to identify the proxy
    • Location: Optional, for your reference only
    • Host: IP/Hostname used to reach the proxy
    • Port: Port where the Fyde Access Proxy will be available
  • Click Create

    Add Fyde Access Proxy

  • Copy the link that will be used when configuring the proxy

  • Please Note: This is the only time the link is provided by the Management Console

    Add Fyde Access Proxy 2

2. Install Fyde Access Proxy in Docker

  • In this quick start we recomend installing the solution using the docker infrastructure, for other platforms please visit Fyde Access Proxy - Install steps

  • The public port will need to be available for the clients connecting to resources

  • The required images are available in Dockerhub registry under the organization FydeInc

  • Requires a valid Fyde Access Proxy enrollment link, obtained in the previous step

  • Minimum OS supported versions:
    • Debian 9
    • Centos 7
    • Ubuntu 16.04
    • MacOS 10.14
  • Please note that the steps below will execute scripts obtained externally

  • We advise to inspect the content before execution

  • Choose yes, when questioned about installing the test resource

  • Download and execute installation script

      sudo bash -c "$(curl -fsSL"

3. Add new resource

  • In this step we are going to create a test resource, however you can use an existing resource of your own instead

  • To add a new resource, go to Access and click the “+” icon in the top right.

    Control Screen

  • Fill in the details:

    Add Resource

    • Resource Name: HTTP Test

    • Public Host: http.test.local

    • Resource Host: httptest

    • External Port: 81

    • Internal Port: 80

    • Access Proxy: Select the existing Fyde Access Proxy

    • Policy Name: Allow Everyone

    • Notes: Leave empty

  • Click Create

4. Add new user

  • In order to register a device, we need to create a user

  • Users and account administrators are separate entities. The same email can be used for account administrators and a regular user and there will be no relation between them

  • To add a new user, go to Identity and click the “+” icon in the top right.

    Control Screen

  • Add the following:

    • Name: Name to identify the user

    • Email: Required to send the enrollment to the user link via email

    • Phone: Optional, for your reference only

    • Group: Optional, groups that the user is part of

  • Select Send email invitation (optional) to send and email to the user with enrollment steps

  • Click Create

    Add User

5. Enroll a device

  • A user can have multiple devices, this will be determined by the account administrators

  • Enroll a new device for the created user by acessing the enrollment link
    • The link is sent to the email configured for the user or by sharing the link from the user details
  • The enrollment process is done directly from the created user’s device

6. Access created resource

  • The enrolled device will now access the created resource

  • Access the configured resource by visiting the following link from the enrolled device:


  • If the device is not accessing the resource please visit: Troubleshooting for troubleshooting steps