For additional security, virtual channel plugins can be signed, and the digital signature can be verified. Before loading a virtual channel plugin, the Anyware agent will verify if the plugin has a valid digital signature and takes action based on the configured signing policy.
The following table describes the verification policies:
This section describes how to replace HP's default certificates with your own custom certificates.
Note: These procedures use OpenSSL
This topic contains example procedures that illustrate how to configure Ubuntu and RHEL machines for smartcard authentication.
Cloud-based Ubuntu hosts will fail to properly identify Wacom tablets that have been locally-terminated at the Anyware client. When this occurs, pressure sensitivity and other advanced features will not work properly.
To work around this issue, remove the default AWS, Microsoft Azure, or Google Cloud kernel and replace it with a generic kernel.
Note: Ubuntu cloud hosts only
You can use the Standard Agent for Linux to provide brokering capabilities for your Linux Remote Workstation Card machines.
Important
Configuring your Anyware Zero Client's connection mode as described here will disable direct-to-host connections.
Licensing issues with the Cloud License Service (CLS) might occur if the Amazon Root CA 1-4 certificates are not in the certificate bundle of your system. Therefore, updating your operating system is the quickest way to ensure that your system has these certificates.
Important
The Standard Agent for Linux supports IPv6 addresses. No configuration is needed to switch between IPv4 and IPv6 modes.
This guide is intended for administrators who are deploying the Standard Agent for Linux as part of HP Anyware. It assumes thorough knowledge of Linux conventions and networking concepts, including firewall configuration.
Anyware clients can connect to your desktops hosted in proof-of-concept, cloud, or datacenter deployments.