Skip to main content

Changes between 9.3 and 19.07

The SecureAuth® Identity Platform was created for organizations that want or need a cloud or hybrid solution. The SecureAuth IdP 9.3 user interface (UI) was updated to transition it to move to the cloud, with ease of use at the forefront of the design. These changes mean that existing customers will see similarities and differences as they move between the two UIs.

Admins will use the SecureAuth® Identity Platform New Experience to configure and manage some aspects of the environment, but will also use the Classic Experience to configure and manage other features, such as endpoint products.

The following table maps terms, concepts, and features that you know from using SecureAuth IdP to new terms, concepts, and features in the SecureAuth Identity Platform.

9.3 and earlier

19.07 and later


SecureAuth IdP, New Experience

SecureAuth Identity Platform

The product name has changed to SecureAuth Identity Platform, with Identity Platform as the short name. Earlier product names will remain the same for version 9.3.x and earlier.


Cloud, hybrid, on-premises

SecureAuth IdP version 9.2 and earlier were mainly on-prem solutions, with the SecureAuth IdP version 9.3 redesign positioning the product in the cloud space. The Identity Platform adds more robust cloud and hybrid features.

SecureAuth IdP UI

Classic Experience

When discussing user interfaces, the SecureAuth IdP 9.3 UI is referred to as the New Experience; the 9.2 and earlier UI is referred to as Classic Experience. Starting in 9.3, customers were able to toggle between the New Experience and the Classic Experience.

Versions incremented numerically

Versions increment by release date

The product versioning scheme has changed. SecureAuth IdP version 9.3 was the previous version; SecureAuth IdP 9.3 and earlier version increments will not change. The scheme from the current version and later will be based on the year, month, and point release (.01) or feature release (1) number.

Example: The current release is 19.07, which stands for the year (19) and month (7) of the release. This is a new release, so there is no point or feature release number.

Adaptive Authentication, workflow


Policies are a set of rules that impact the login experience for a given set of applications. Policies existed in SecureAuth IdP 9.3 and earlier, with admins configuring adaptive authentication rules and workflows in their respective tabs in each realm. Now admins can set adaptive authentication rules and certain workflow settings in a policy to use against a set of applications in the Identity Platform.



In SecureAuth IdP version 9.3 and earlier, each application had to be set up in a separate realm. In the Identity Platform, you can use the Application Manager to configure multiple applications in one place for all version 19.07 realms.


SecureAuth Connector

The SecureAuth Connector was added to support the move to the cloud. Admins install and configure the Connector to establish communication between the local identity data store and the SecureAuth Identity Platform. See the SecureAuth Identity Platform architecture to view a diagram that shows the placement of the Connector.



The Identity Security Intelligence dashboard provides key login, multi-factor authentication (MFA) method, and other metrics at a glance.

Authenticate app

No name changes

Globally define which multi-factor authentication (MFA) methods are available for end users in the Identity Platform Application Manager. Provision MFA methods in realms in the Classic Experience. Enable specific MFA methods to determine which factors end users can use during authentication.

MFA vs. 2FA

No name changes

SecureAuth uses multi-factor authentication if discussing all three factors and in information directed at administrators. For information directed at end users (or admins who will cascade the info to end users), SecureAuth uses two-factor authentication or 2FA.

Fingerprint recognition

Biometric MFA

The general term Biometric MFA is used to describe all forms of biometric login, while facial and fingerprint recognition are used to discuss the specific biometric type used during log in.

One-time Passcode

Notification Passcode

This is a terminology change to offer clearer user experience to end users. Admins might see either term in documentation and the product.

Time-based One-time Passcode

Timed Passcode

This is a terminology change to offer clearer user experience to end users. Admins might see either term in documentation and the product.

Login Request, push-to-accept, symbol-to-accept

Login Notification

This is a terminology change to offer clearer user experience to end users. Admins might see either term in documentation and the product.