Configuring an Horizon Accesspoint (the easy way)

Configuring an Horizon Accesspoint (the easy way)

The new Horizon accesspoint can be configured via REST and for that we even have a swagger UI as well as a config documentation.




https:// [FQDN]:9443/swagger-ui/index.html

The swagger will be located on your Backend Or Management NIC of the Accesspoint.

Accessing the Swagger UI

  1. Open a browser and browse to https:// [FQDN]:9443/swagger-ui/index.html
  2. Authenticate with admin and the password you specified at deployment.
  3. You see the picture below


Change the SSL Certificate

  1. Click on ServerCertificate
  2. Then Click on PUT /v1/config/certs/ssl
  3. Click on the side (Model Schema). This will transfer the values into the body
  4. Copy the Values into a notepad
  5. Replace the String(s) with the Private Key and with the Certificate chain.
  6. Copy/Paste the notepad content back into the body
  7. Click on Try it out.
  8. Check the result.

Changing the Connection settings

These settings make sure that the Accesspoint can connect to the Conenction Server (or its load balancer) as well as make sure that the tunnels are terminated at the correct point.

  1. Click on EdgeServiceSettings
  2. Click on GET /v1/config/edgeservice
  3. Click on Try it Out!
  4. Copy the Response Body into a notepad
  5. Edit the settings as required. Also you ONLY need the part shown below, not the JSON array {[…]} around it.


"identifier": "VIEW",

"enabled": true,

"proxyDestinationUrl": "https://connection1.mylab.local:443",

"proxyDestinationUrlThumbprints": "sha1=42 41 ba da 3b 58 4b 59 01 b1 66 38 01 59 26 28 78 5d 3a 0a",

"pcoipEnabled": true,

"pcoipExternalUrl": "",

"blastEnabled": true,

"blastExternalUrl": "access1.mylab.local:8443",

"tunnelEnabled": true,

      "tunnelExternalUrl": "access1.mylab.local:443",

"proxyPattern": "/",

"matchWindowsUserName": false,

"gatewayLocation": "External",

"windowsSSOEnabled": false


  1. Copy the settings
  2. Click on PUT /v1/config/edgeservice/view
  3. Past the settings into body
  4. Click on Try it out!
  5. The response should be 200. Anything else (400 and more) indicates an error.



There can be problems if your certs are not up to scratch. In that case you may need to clear your cache. Clearing the cache in Crome is done by pressing [CTRL] + [Shift] + [DEL].

Im currently working on a VRO Package for might be a bit in the making...Im very bussy.

Version history
Revision #:
1 of 1
Last update:
‎08-08-2016 06:01 AM
Updated by: