Changes between 19.07 and 20.06
Organizations that want or need a cloud or hybrid solution with ease of use at the forefront of the design, will find a lot to like in the SecureAuth® Identity Platform release 20.06. Existing customers will see the new features discussed briefly in the following table.
Admins will use the Identity Platform release 20.06 New Experience to configure and manage more aspects of the environment than in release 19.07, but will also use the Classic Experience to configure and manage other features, such as the Authenticate mobile app and other SecureAuth apps.
The following table maps terms, concepts, and features that you know from using the Identity Platform 19.07 to new terms, concepts, and features in the Identity Platform 20.06.
For a list of all enhancements, updates, and known issues for the current release, see the Release notes.
9.3 and earlier | 19.07 and later | Differences | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
--- | FIDO2 WebAuthn support | The Identity Platform supports the use of FIDO2-enabled devices that use the WebAuthn protocol. Using FIDO2-enabled devices provides strong authentication with a passwordless login workflow for better user experience. | ||||||||||||||||||
Supports two data stores | Supports more data stores |
| ||||||||||||||||||
Version 1.0 of UI look and feel | Enhanced UI look and feel | The Identity Platform UI was refreshed and now has a more modern and colorful look. This is especially evident in the dashboard (available by clicking the Home link on the left navigation), where colors help to delineate the different properties for methods, applications, and OS's. | ||||||||||||||||||
Adaptive IP Blocking, supported WS-Trust workflows only | Dynamic IP Blocking | New in release 20.06, the feature name was changed to better describe the dynamic way that SecureAuth uses IP blocking to enhance security. | ||||||||||||||||||
Authenticate app | Pre-populate the Authenticate enrollment URL | Companies that manage employee mobile devices through a mobile device management (MDM) tool that supports the AppConfig Community standard can pre-populate the Authenticate enrollment URL. This allows end users to bypass entering the enrollment URL so they only need to register their account to authenticate |