Here’s a simple process for hooking your ThinApp Factory appliance into your Horizon environment.
Procedure for adding Horizon Settings to ThinApp Factory for App Publishing to Horizon:
- Login to Horizon as an Administrator.
- Go into Settings under Admin.
- Under Identity Provider, click Add Identity Provider.
- Type in the Provider name and comments.
- Remove the IP range so none exists!
- Click save, then copy the Connector Activation Code.
Note: You may also wish to set the priority of this connector low.
- Open ThinApp Factory, login, and go into the Configuration tab under Settings.
- Check the Enable publish to Horizon check box.
- Type in the Horizon Organization URL and paste in the Connector Activation Code, then click Validate & Save in the box.
- IMPORTANT – Scroll to the bottom of the configuration tab page and click the Save button!
Adding ThinApp Factory packages to Horizon:
Now, when editing, importing or creating projects, you will have the option to “Horizon enable” the ThinApp project/package. When it gets PUBLISHED from the ThinApp Factory Projects page, it will then show in the Horizon Manager Applications tab for Horizon Administrators to assign to users or groups.
To make ThinApp Factory “Horizon Enabled” one must add a new Horizon Org “Identity Provider”. This can be done under the Identity Provider settings when logged in as a Horizon ORG Administrator.
When adding a new Horizon Org “Identity Provider” for use with ThinApp Factory, ensure there are NO IP Pools defined!!
By default a new Identity Provider will add a default IP Pool range of 0.0.0.0 – 255.255.255.255. Leaving this default setting may cause issues if none of the defined Horizon Connectors have an IP Pool of 0.0.0.0 – 255.255.255.255.
To remove the default IP Pool, simply move the mouse to the right of the right-hand block and you will see the RED “X”. Click this to remove the IP Range.
Symptoms Seen When Default IP Pool Range Settings are Set Incorrectly:
Error 1: Identity Provider does not have metadata specified
Error 2: The sign in page has not yet been configured. Contact your Administrator for help
The above errors can be seen with any non-user identity provider specified if IP ranges are improperly defined and the non-user identity providers are selected for user authentication.