...
Note that this topic does not cover security access controls in the virtual assets or message proxies that are accessed by the application under test (AUT). That is addressed in Working with Message Proxies and Configuring for Services Deployed Over HTTPS.Configuring for Services Deployed Over HTTPS.
About Virtualize Server User Access Control
| Anchor | ||||
|---|---|---|---|---|
|
...
| 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. |
...