To launch remote desktops and applications from Workspace Portal or to connect to remote desktops and applications through a third-party load balancer or gateway, you must create a SAML authenticator in View Administrator. A SAML authenticator contains the trust and metadata exchange between View and the device that client connect to.
About this task
You associate a SAML authenticator with a View Connection Server instance. If your deployment includes more than one View Connection Server instance, you must associate the SAML authenticator with each instance.
For information about configuring a SAML authenticator for VMware Access Point appliances, see Deploying and Configuring Access Point.
Verify that Workspace Portal or a third-party gateway or load balancer is installed and configured. See the VMware Workspace Portal Portal Installation and Configuration Guide.
Verify that the root certificate for the signing CA for the SAML server certificate is installed on the View Connection Server host. VMware does not recommend that you configure SAML authenticators to use self-signed certificates. For information about certificate authentication, see the View Installation document.
Make a note of the FQDN or IP address of the Workspace Portal server or external-facing load balancer.
For Workspace Portal, make a note of the URL of the Workspace Portal Connector Web interface.
- In View Administrator, select View Configuration > Servers.
- On the Connection Servers tab, select a View Connection Server instance to associate with the SAML authenticator and click Edit.
- On the Authentication tab, select a setting from the Delegation of authentication to VMware Horizon (SAML 2.0 Authenticator) drop-down menu to enable or disable the SAML authenticator.
SAML authentication is disabled. You can launch remote desktops and applications only from Horizon Client.
SAML authentication is enabled. You can launch remote desktops and applications from both Horizon Client and Workspace Portal or the third-party device.
SAML authentication is enabled. You can launch remote desktops and applications only from Workspace Portal or the third-party device. You cannot launch desktops or applications from Horizon Client manually.
You can configure each View Connection Server instance in your deployment to have different SAML authentication settings, depending on your requirements.
- Select Create New Authenticator from the SAML Authenticator drop-down menu, or, if a SAML authenticator has already been added, click Manage Authenticators and click Add.
- Configure the SAML authenticator in the Add SAML 2.0 Authenticator dialog box.
Unique name that identifies the SAML authenticator.
Brief description of the SAML authenticator. This value is optional.
URL for retrieving all of the information required to exchange SAML information between the SAML identity provider and the View Connection Server instance. In the URL https://<YOUR HORIZON SERVER NAME>/SAAS/API/1.0/GET/metadata/idp.xml, click <YOUR HORIZON SERVER NAME> and replace it with the FQDN or IP address of the Workspace Portal server or external-facing load balancer (third-party device).
URL for accessing the administration console of the SAML identity provider. For Workspace Portal, this URL should point to the Workspace Portal Connector Web interface. This value is optional.
- Click OK to save the SAML authenticator configuration.
If you provided valid information, you must either accept the self-signed certificate (not recommended) or use a trusted certificate for View and Workspace Portal.
The SAML 2.0 Authenticator drop-down menu displays the newly created authenticator, which is now set as the selected authenticator.
- In the System Health section on the View Administrator dashboard, select
, select the SAML authenticator that you added, and verify the details.
If the configuration is successful, the authenticator's health is green. An authenticator's health can display red if the certificate is untrusted, if Workspace Portal is unavailable, or if the metadata URL is invalid. If the certificate is untrusted, you might be able to click Verify to validate and accept the certificate.
What to do next
Extend the expiration period of the View Connection Server metadata so that remote sessions are not terminated after only 24 hours. See Change the Expiration Period for Service Provider Metadata.