D251: Duo Release Notes for Oct 14, 2022

[timshores1]

Hello everyone! Here are the release notes for our most recent updates 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

• Duo Central Device Management is Now in General Availability
• Duo Passwordless Platform Authenticators Now Support Multi-Device Authentication
• Verified Duo Push and Risk-Based Factor Selection Policies Now Let Administrators Set Verification Code Length
• Updated Certificate Issuer Name for Azure SCEP Certificate Profiles In Microsoft Intune Managed Endpoint Device Deployment

New and updated applications

• Duo Device Health Application Stable Release for macOS and Windows 3.1.0
• Duo Device Health Application Public Beta for macOS and Windows 3.0.1
• Duo Mobile 4.26.0 for Android
• Duo Mobile 4.26.0 for iOS

---

New features, enhancements, and other improvements

Duo Central Device Management is Now in General Availability

• Check the Allow users to add and delete devices via the self-service portal when they log in through Duo Central to allow access to device management for enrolled users as they log in to Duo Central to access SSO applications and other bookmarked apps.

Duo Passwordless platform authenticators now support multi-device authentication

• Passwordless now supports the use of WebAuthn passkeys created with platform authenticators that synchronize private keys within their device ecosystem.
• For example, when an end-user enrolls one compatible Apple device with Face ID or Touch ID as a Duo authenticator, they can immediately use their other Apple devices with Face ID or Touch ID as Duo authenticators.
• Platform authenticators must be enabled as a Passwordless authentication method to support multi-device authentication.

Verified Duo Push and Risk-based factor selection policies now let administrators set verification code length

• Verified Duo Push verification code has a minimum and default length of 3 digits, and a maximum length of 6 digits.

• Risk-based factor selection verification code has a minimum length of 3 digits, and a maximum and default length of 6 digits.

• When receiving a Verified Duo Push, Duo Mobile will present a number of fields that corresponds to the effective policy.

Updated certificate issuer name for Azure SCEP certificate profiles in Microsoft Intune Managed Endpoint Device Deployment

• Newly created SCEP certificate profiles will show a Subject Name Format value of CN=Duo Endpoint Validation Issuing CA 2.
• Administrators may update the Subject Name Format value in existing SCEP certificate profiles to match the new certificate issuer common name, but it is not necessary.

New and updated applications

Duo Device Health application stable version 3.1.0 released

• macOS stable version 3.1.0.0
  • Minor improvements and enhancements.
• Windows stable version 3.1.0
  • Fixed an issue that could prevent update from occurring on non-English installation of Windows.

Duo Device Health application public beta version 3.0.1 released

• macOS beta version 3.0.1.0
  • Minor improvements and enhancements.
• Windows beta version 3.0.1
  • Minor improvements and enhancements.

Duo Mobile for Android version 4.26.0 released

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

Duo Mobile for iOS version 4.26.0 released

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

[hawley.35]

Where are the release notes for D252? Our Admin Panel shows version 252, but there appear to be no release notes.

[DuoKristina]

Hi @hawley.35 ,

We publish these public notes every other Friday after a D-release completes deployment to commercial customers. So, you can expect the D252 notes post tomorrow.

[owenhael]

Would it be possible to get release notes when the deployment starts (or earlier) instead of after it finishes?

[timshores1]

Hi @owenhael thank you for posting your question. I think your suggestion is worth exploring. At this time, it’s not possible given our process of developing in biweekly sprints. A fair amount of work goes into orchestrating several engineering and QA teams to organize, clarify, and verify the accuracy of Release Notes before we’re ready to publish here.

[owenhael]

Hi Tim, I’m not sure I understand. How do biweekly sprints preclude putting release notes out at the start of the release or beforehand? Duo is a mission-critical application and having release notes in advance so administrators know what to look for in case of issues is pretty standard.

[timshores1]

Hi Owen, I’m sorry to be unclear … I mean that our current process of orchestrating info from several teams is what locks me into the current timing of posting Release Notes a day after the release is completed. Historically, this practice was meant to avoid the back-and-forth of Release Notes updates and revisions when specific changes are rolled back when acceptance testing discovers problems in the final deployment.

All that said, I think you make a good suggestion, and I’m already discussing with others at Duo how we can make it happen. Just takes time and coordination of multiple teams.

[owenhael]

Thank you Tim, all I can ask for is consideration. Thanks for responding to my questions here.