Sep 13, 2023 ‚ÄĒ Authentication Page and My Devices Page Refresh

New features and enhancements

This release brings a refreshed user interface (UI) to the authentication prompt and Manage My Devices page.

The following are the Authentication page changes:

  • All enrolled devices are now displayed at once in expandable device cards.
  • The last used device's card is expanded automatically on page load.
  • Devices are ordered in the following manner:
    • Mobile (Push) device -> Security Key device -> Phone Number Only device -> Hardware Token device (HOTP/TOTP) -> External TOTP app
    • If more than one type of the same device is present, the newest one is displayed on top.
  • Device cards display the enrollment date of the device.

The following are the Manage My Devices page changes:

  • Device cards display the enrollment date of the device.
  • Selecting default devices and their automatic actions is no longer available.
  • You can enable automatic challenge for your last used authentication factor.
    • Security Key devices now support automatic challenges.
    • TOTP/HOTP and browser-extension based factors don't currently support automatic challenges.
    • Automatic challenge is disabled by default for new users and newly enrolled devices.
    • Automatic challenge is enabled by default for users who previously had a default device and factor set up.

Fixed issues

  • Automatic FIDO2 security key push authentication now properly shows a toast message.

Known issues

  • On Firefox, starting a security key authentication and canceling it may cause the device to not be able to process a subsequent challenge properly. The workaround is to cancel and restart again, which should allow the challenge to succeed.
  • Users using the Windows Logon plug-in and attempting to unlock the Windows locked screen may sometimes encounter errors entering just the username.
    Workaround: Users may try entering domain\username in the username field to unlock the screen.
  • Clicking the ‚ÄúHelp‚ÄĚ link present in the ‚ÄčAkamai MFA‚Äč authentication prompt may not open the link in the webview presented inside an application‚Äôs client, such as the WebEx client, that is used to authenticate with MFA for that application. As an alternative, the user may enter <<MFA_DOMAIN>>/help in a standard web browser and reach the same destination.

Supported browser versions

The following are the minimum browser versions that support the ‚ÄčAkamai MFA‚Äč browser extension:

  • Firefox 87.0

  • Google Chrome 89.0.4389.90

  • Microsoft Edge 89.0.774.57

  • Safari 14.0.3

Internet Explorer is not supported.

Supported mobile devices versions

The following mobile device OS versions support the ‚ÄčAkamai MFA‚Äč mobile app:

  • iOS 13 and above (iPad, iPhone, iPod Touch)

  • Android 7 and above (phones and tablets)

Supported Windows versions

The following Windows versions support the ‚ÄčAkamai MFA‚Äč Windows Logon plug-in:

  • Clients: Windows 10
  • Servers: Windows Server 2012 R1 Standard (legacy plug-in), Windows Server 2012 R2, 2016, and 2019