Versions Compared

Old Version 1

changes.mady.by.user user-50d80

Saved on

compared with

New Version Current

changes.mady.by.user Chieko Sugizaki

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space FUNCTDEV and version SVC2021.1

...

  1. Connect the Virtualize Server to CTP via Preferences> CTP. See CTP Settings for details.

    Note
    titleHTTPS Note

     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., 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). 

  2. If you have not already done so, use CTP to configure user accounts and permissions. For details, see the CTP User’s Guide.

...



Note
titleHTTPS 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.


...