Administration

Table Of Contents
Prerequisites
Verify that you have created a SAML authenticator for the identity provider: Unified Access Gateway or a
third-party load balancer or gateway. In the System Health section on the Horizon Administrator
dashboard, you can select Other components > SAML 2.0 Authenticators, select the SAML
authenticator that you added, and verify the details.
Procedure
1 Open a new browser tab and enter the URL for getting the Connection Server SAML metadata.
https://connection-server.example.com/SAML/metadata/sp.xml
In this example, connection-server.example.com is the fully qualified domain name of the Connection
Server host.
This page displays the SAML metadata from Connection Server.
2 Use a Save As command to save the Web page to an XML file.
For example, you could save the page to a file named connection-server-metadata.xml. The
contents of this file begin with the following text:
<md:EntityDescriptor xmlns:md="urn:oasis:names:tc:SAML:2.0:metadata" ...
What to do next
Use the appropriate procedure on the identity provider to copy in the Connection Server SAML metadata.
Refer to the documentation for Unified Access Gateway or a third-party load balancer or gateway.
Response Time Considerations for Multiple Dynamic SAML
Authenticators
If you configure SAML 2.0 Authentication as optional or required on a Connection Server instance and
you associate multiple dynamic SAML authenticators with the Connection Server instance, if any of the
dynamic SAML authenticators become unreachable, the response time to launch remote desktops from
the other dynamic SAML authenticators increases.
You can decrease the response time for remote desktop launch on the other dynamic SAML
authenticators by using Horizon Administrator to disable the unreachable dynamic SAML authenticators.
For information about disabling a SAML authenticator, see Configure a SAML Authenticator in Horizon
Administrator.
Configure Workspace ONE Access Policies in Horizon
Administrator
Workspace ONE, or VMware Identity Manager (vIDM) administrators can configure access policies to
restrict access to entitled desktops and applications in Horizon 7. To enforce policies created in vIDM you
put Horizon client into Workspace ONE mode so that Horizon client can push the user into
Workspace ONE client to launch entitlements. When you log in to Horizon Client, the access policy
directs you to log in through Workspace ONE to access your published desktops and applications.
View Administration
VMware, Inc. 74