A Horizon administrator can use the Unauthenticated Access feature to create Unauthenticated Access users and entitle those users to published applications on a Connection Server instance. Unauthenticated Access users can log in to the server anonymously to connect to their published applications.
Perform the administrative tasks described in Preparing Connection Server and Security Servers.
Set up Unauthenticated Access users on the Connection Server instance. For information, see "Providing Unauthenticated Access for Published Applications" in the Horizon 7 Administration document.
- To connect to the Connection Server instance on which you have unauthenticated access to published applications, open a browser and use one of the following URI syntaxes.
authority-part specifies the server address and, optionally, a non-default port number. Server names must conform to a DNS syntax. To specify a port number, use the following syntax: server-address:port-number. anonymous_account is the Unauthenticated Access user account created for logging in anonymously.
Connections to Connection Server always use TLS. The default port for TLS connections is 443. If Connection Server is not configured to use the default port, use the format shown in this example: horizon.company.com:1443.
- (Optional) If you did not specify the unauthenticatedAccessAccount query, select an Unauthenticated Access user account from the User account drop-down menu, if necessary, and click Submit.
If only one Unauthenticated Access user account is available, the user account is selected by default.
The application selection window appears.
- Click the icon for the published application that you want to access.
The published application appears in your browser. A navigation sidebar is also available. You can click the tab at the left side of the browser to show the sidebar. You can use the sidebar to access other published applications, show the Settings window, copy and paste text, and more.Note:
You cannot reconnect to unauthenticated application sessions. When you disconnect from the client, the RDS host logs off the local user session automatically.