If you have an Unauthenticated Access user account, you can log in to a server anonymously and connect to your published applications. The connection procedure is slightly different for administrators and end users, so refer to the section that applies to your role.
Procedure for End Users
Before you begin, get the following information from your administrator:
- Server name to use for connecting to the server.
- An Unauthenticated Access user account to use for logging in anonymously.
-
To connect to the server on which you have unauthenticated access, open a browser and enter a Uniform Resource Identifier (URI).
For example, you can use one of the following URI syntaxes.
- https://authority-part?unauthenticatedAccessEnabled=true
- https://authority-part?unauthenticatedAccessEnabled=true&unauthenticatedAccessAccount=anonymous_account authority-part is the server address and, optionally, a non-default port number. If you need to specify a port number, enter server-address:port-number.
anonymous_account is the Unauthenticated Access user account.
Connections always use TLS. The default port for TLS connections is 443. If the 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 an Unauthenticated Access user account in the URI, 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, that user account is selected by default.
The application selection window appears after you click Submit.
-
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 on the left side of the browser window 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, you are logged off the local user session automatically.
Procedure for Administrators
Verify that you have completed the following prerequisites:
- Perform the administrative tasks described in Preparing Omnissa Horizon Connection Server.
- Set up Unauthenticated Access users on the Horizon Connection Server instance. For information, see "Providing Unauthenticated Access for Published Applications" in the Horizon Administration document.
-
To connect to the server on which you have unauthenticated access, open a browser and enter a Uniform Resource Identifier (URI).
For example, you can use one of the following URI syntaxes.
- https://authority-part?unauthenticatedAccessEnabled=true
- https://authority-part?unauthenticatedAccessEnabled=true&unauthenticatedAccessAccount=anonymous_account authority-part is the server address and, optionally, a non-default port number. If you need to specify a port number, enter server-address:port-number.
anonymous_account is the Unauthenticated Access user account.
Connections always use TLS. The default port for TLS connections is 443. If the 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 an Unauthenticated Access user account in the URI, 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, that user account is selected by default.
The application selection window appears after you click Submit.
-
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 on the left side of the browser window 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, you are logged off the local user session automatically.
Was this page helpful?