Duo Release Notes for May 22, 2020

Hello everyone! Here are the release notes for the most recent updates we’ve made to Duo.

You can subscribe to notifications for new release notes by following the process described here. If you have any questions about these changes, please comment below.

What’s in this release?

New and updated applications

New features, enhancements, and other improvements

Bug fixes

See all bug fixes


New and updated applications

Duo Authentication Proxy version 4.0.0 released

  • The Authentication Proxy is now packaged with and runs on Python 3.
  • When installed on Windows, directory permissions restrict access to the conf folder to the built-in Administrators group.
  • Improved directory sync performance when syncing large groups from Active Directory.
  • Fixed a bug causing RADIUS authentications to fail for usernames with non-ASCII characters.
  • Duo application ikey values are now properly captured in the authentication log during RADIUS authentication.

Duo Unix 1.11.4 released

  • Added support for Ubuntu 20.04.
  • Added support tool to collect information (e.g. logs and PAM stacks) you can send to Duo Support when troubleshooting issues.
  • Ubuntu 12.04 no longer supported.
  • Updated GPG public key for downloading distribution packages.

Duo Mobile for iOS version 3.33.2.3 released

  • Minor UI updates to improve usability on modern phones.
  • Other minor improvements.

Applications added for the public beta of Duo Single Sign-On

Duo Device Health Application version 2.4.0.0 released

  • Reduced certificate validity period to prevent communication issues with the app in certain browsers.

New features, enhancements, and other improvements

Cisco Meraki Systems Manager integration added for Duo Trusted Endpoints

  • Duo Trusted Endpoints now integrates with Cisco Meraki Systems Manager. This integration allows Duo administrators who manage their device fleet with Meraki Systems Manager to use Duo’s Trusted Endpoints policy to check if an iOS or Android device is managed by Service Manager at the time of access and manage access accordingly.
  • This integration is available to customers on the Duo Beyond plan.

Directory Sync now supports manually synchronizing up to 50 users at once

Duo Mobile for Trusted Endpoints can now be enabled for a specific mobile OS

  • Administrators using Duo Mobile to check a device’s managed status via Trusted Endpoints can now choose whether to enable the feature for either iOS and/or Android.
  • This allows organizations to use a different mobile device management solution in combination with Duo Mobile as a device verification tool via Trusted Endpoints.

Improved message wording in the Admin Panel when reordering application group policies, entering a custom Help Desk message

  • When reordering a custom group policy on an application’s properties page in the Admin Panel, the message that appears when moving a group policy to the top of the priority list is now more clear.
  • When entering a custom Help Desk message on the Settings page, the prompt text for the field now clarifies where the message will be displayed, depending on a customer’s Duo billing edition.
    • The Help Desk field itself has also been expanded to a multi-line input field to make it easier to enter and edit text. It still supports up to 200 characters, as before.

Bug fixes

  • Fixed an issue in which old bypass codes were not ordered correctly when sorting by the “Created On” column in the list of bypass codes that appears in the Admin Panel.
  • Fixed a bug in which some group changes associated with an on-premises directory sync, including the addition and removal of groups, were not reported correctly in the Administrator Actions log in the Admin Panel.
  • Fixed an issue in which enrollment events were not appearing in the Authentication Log if a user enrolled a new device as a tablet via the Self-Service Portal.
  • Improved the wording of an error message that appears as a result of a failed directory search to suggest a second possible reason for the issue (incorrect Authentication Proxy configuration).