This site will be decommissioned on December 31st 2024. After that date content will be available at techdocs.broadcom.com.

VMware Workspace ONE Access for Linux 20.10.0.1 | February 2021 | Build 17586971

Released February 2021

VMware Workspace ONE Access 20.10.0.1 is a patch release, resulting in abbreviated release notes. The content of the VMware Workspace ONE Access Release Notes for 20.10 apply to this version as well.

Updated

  • December 17, 2021

12/17/2021 This release has been determined to be impacted by CVE-2021-44228 and CVE-2021-45046. Fixes and workarounds are available to address this vulnerability. For more information, see VMware Security Advisory VMSA-2021-0028.

12/17/2021 This release is also impacted by CVE-2021-22056 and CVE-2021-22057. Fixes and workarounds are available to address this vulnerability. For more information, see VMware Security Advisory VMSA-2021-0030.

What's New

The 20.10.0.1 patch release addresses the deployment issues for deployments with no outbound access to the internet.

Installation and Upgrade Information

To install or upgrade to Workspace ONE Access for Linux 20.10,0.1, see the 20.10 release notes and the 20.10 documentation in the Workspace ONE Access Documentation center. During the upgrade, all services are stopped; plan the upgrade with the expected downtime in mind.

Resolved Issues

  • HW-130756 - Fixed the issue that prevented 20.10 to run successfully when the appliance does not have direct outbound internet connectivity.
  • HW-130757 - Fixed the issue related to update scripts using space in root partition. See this KB 81994 article for more details about this  issue.
  • HW-130760 - This release includes the fix for the issues in VMSA-2020-0027.
  • HW-130944 - Fixed the issue that caused the Notification (For You) feature not to work when Workspace ONE Access was configured with SQL Server Windows Authentication.

Known Issues

  • Network Not Found after Upgrading to 20.10.0.1

    Network lost after the upgrade to 20.10.0.1 due to missing vm.vmname ovf property

    Workaround

    Execute the command from the appliance - /opt/vmware/bin/ovfenv and check the value of [vm.vmname] from the output. If the vm.vmname is emtpy, follow the steps below to resolve the issue:

    1. Shut down the Virtual Machine
    2. Edit the Virtual Machine vApp Options to update the default value of the vm.vmname property to "IdentityManager"
    3. Restart the Virtual Machine. The network will come up.
  • RabbitMQ is not coming up after upgrade to 20.10.0.1

    RabbitMQ is not coming up after upgrade to 20.10.0.1 and 20.10 due to missing softlink of /var/lib/rabbitmq/.erlang.cookie.

    After using SSH to log in to the appliance and executing ls -l /root/.erlang.cookie, verify if it is pointing to /var/lib/rabbitmq/.erlang.cookie and the output is similar to "lrwxrwxrwx 1 root root 32 Feb 10 14:34 /root/.erlang.cookie -> /var/lib/rabbitmq/.erlang.cookie". Use the workaround if this is not the case.

    Workaround
    1. SSH into the Workspace ONE Access appliance as the root user.
    2. Stop the RabbitMQ service: systemctl stop rabbitmq-server.service
    3. Run the following commands:
        rm -f /root/.erlang.cookie
        In -s /var/lib/rabbitmq/.erlang.cookie /root/.erlang.cookie
    4. Start the RabbitMQ service:
        systemctl start rabbitmq-server.service
    5. To verify that RabbitMQ is running, type
        systemctl status rabbitmq-server.service
    6. To verify that RabbitMQ queues are created, type
        rabbitmqctl list_queues

check-circle-line exclamation-circle-line close-line
Scroll to top icon