D234: Duo Release Notes for February 18, 2022

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 features, enhancements, and other improvements

New and updated applications

Bug fixes

See all bug fixes


New features, enhancements, and other improvements

Deprecation timeline announced for Duo Access Gateway

  • As of February 15, 2022, Duo has announced the deprecation timeline for Duo Access Gateway for Duo MFA, Access, and Beyond edition customers. Duo Access Gateway will continue to be supported for GovCloud and FedRamp customers. The recommended action is to migrate to Duo Single Sign-On, our cloud-hosted replacement solution.
  • Refer to the timeline below to understand important milestones:
    • February 15, 2022: Deprecation timeline announced via email to current DAG customers. In addition, as of February 3, new Duo customers may no longer create new DAG implementations.
    • May 19, 2022: Current DAG customers will no longer be able to create new DAG integrations. Existing DAG integrations and the DAG Launcher will continue to work normally until the end-of-life date and are considered supported until that date.
    • October 2023: Target DAG end-of-life. DAG implementations will no longer be able to connect to Duo’s service and will stop working.
  • Documentation: How to migrate from DAG to Duo Single Sign-On

Improvements to the management of inactive Duo administrators

  • Duo administrators whose accounts have expired due to inactivity will now show a status of Expired in the Administrators list in the Duo Admin Panel. When viewing the administrator details page, you will now see the number of days of inactivity and be able to clear their Expired status. Clearing their Expired status is reported in the Administrator Actions Log.
  • In addition, administrators with the status of Expired will be unable to access the Admin Panel.
  • Admins with the status of Expired cannot have their role changed to Owner until their inactivity is cleared, and Owner-role admins cannot be set to a status of Expired in order to enforce at least one active Owner per account. Duo recommends creating at least two administrative users with the Owner role per account.

Duo Device Health application policy workflows now supported for Duo Passwordless, plus additional enhancements to end-user experience

  • Workflows associated with using a Device Health application policy are now supported for Duo Passwordless, which is in public preview.
  • End-users interacting with the Duo Passwordless login flow will also see the following changes:
    • If a user’s browser cookie has expired and they have already enrolled in Duo Passwordless, they will be prompted to log in with an authentication option they have used previously rather than having to choose from a list of available authentication options. Duo will offer a platform authenticator option ahead of other options, depending on the approved options for that user.
    • In addition, in the same cases where an already enrolled user’s cookie has expired, they will no longer see the message “First time logging in here?” and will instead be prompted to authenticate.

New and updated applications

Duo Authentication Proxy version 5.6.0 released, featuring new configuration tool

  • The Windows Authentication Proxy now ships with the Duo Authentication Proxy Manager. This tool provides a user interface for configuring the Authentication Proxy, validating the configuration, and starting or stopping the Authentication Proxy service.
  • The authproxy_connectivity_tool now exits with code 2 if there were any connectivity issues.
  • The Linux Authentication Proxy installer now prompts the user to ask if the SELinux module should be installed if run interactively, and accepts --enable-selinux=yes|no at the command line.
  • Fixed a bug causing the SELinux module installation to not work with custom installation directories.

Duo Mobile for iOS version 4.9.0 released

  • Miscellaneous bug fixes and behind-the-scenes improvements.

Duo Mobile for Android versions 4.8.0 and 4.9.0 released

  • In version 4.8.0:
    • Added support for Portuguese (Brazilian) language.
  • In version 4.9.0:
    • Miscellaneous bug fixes and behind-the-scenes improvements.

Duo Device Health application version 2.22.1.0 for macOS and version 2.22.2.0 for Windows released, as well as public beta versions for macOS and Windows

  • For all released versions:
    • Fixed incompatibility with Google Chrome’s new private network preflight requirements.

Bug fixes

  • Fixed a bug that under certain scenarios resulted in a phone number shared between two Duo administrators being changed for both admins. Now, when an administrator with a shared phone changes their phone number as part of their initial activation of Duo, a new phone will be created and the shared phone number will remain unchanged.
  • On the Settings page in the Admin Panel, the help text for understanding Custom Branding configuration options has been clarified to reflect that testing your branding implementation with a select group of users applies only to the Universal Prompt.
  • Updated the display of Windows OS versions when showing out-of-date information for a Windows endpoint in the Admin Panel to replace verbose numbered versions with more readable versions. Example: Windows 11, version 21H2, instead of 10.0.22000.282.
  • Fixed a bug in which newly created applications for Federal customers defaulted to the Duo Universal Prompt. For information about Universal Prompt support for Federal customers, refer to our documentation.
2 Likes