...
Virtualize Server user access control takes effect whenever the server is configured to connect to a CTP installation. If such a connection is configured and user authentication succeeds, the user will be granted the appropriate level of access. If such a connection is configured but user authentication fails (e.g.for example, because valid credentials were not supplied or because the Virtualize-CTP connection failed), the user will not be granted any access—even read-only access—to the Virtualize Server.
...
- Ensure that the desired roles and access controls for that server are configured in CTP.
- For each Virtualize Desktop previously - connected to the Virtualize Server, re-connect with authentication (i.e.to do so, double-click the existing remote server node in the Virtualize Server view, specify a valid username/password, then save the Server Configuration editor)
...
Connect the Virtualize Server to CTP via Preferences> CTP. See CTP Settings for details.
Note title HTTPS Note If If CTP is deployed over an HTTPS connection (recommended), the Virtualize Server’s CTP connection settings should use an HTTPS URL. This will ensure that the Virtualize Server will communicate with CTP securely over SSL.
If the SSL certificate that CTP is configured with is not trusted by Virtualize Server (e.g.for example, if it is self-signed), you will need to configure the Virtualize Server to trust all certificates—or add that particular CTP certificate to the Virtualize default Java cacerts file and select that option. This can be config-ured in the Preferences> Security settings (as described in Security Settings).
- If you have not already done so, use CTP to configure user accounts and permissions. For details, see the CTP User’s Guide.
...
When adding a remote server, users need to enter a valid username and password in the Add Server dialog.
| Note |
|---|
If you have configured OpenID Connect for authorization (see OpenID Connect in Preferences) for authentication, a statement to that effect will appear instead of username and password fields. |
| Note | ||
|---|---|---|
| ||
By default, the SSL connector (on port 9443) is enabled with a default self-signed certificate, which Virtualize Desktop will trust by default. If the HTTPS option was selected when the remote server was added to the Virtualize Desktop, Virtualize Desktop will communicate with Virtualize Server securely over SSL. If the Virtualize Server certificate is modified with an alternate user-provided keystore (by editing server.xml as described in Configuring SSL (HTTPS) for the Virtualize Server), the client-side certificate (public certificate) should be added to Virtualize Desktop Security preferences as described in Security Settings. This way, Virtualize Desktop will trust that server certificate. Otherwise, the SSL connection might fail because trust establishment would fail. |
Additionally, access levels will be indicated in the server configuration page:
| Anchor | ||||
|---|---|---|---|---|
|
...