The New Experience Web Admin introduced in SecureAuth IdP version 9.3 lets you configure Active Directory and SQL Server data stores, and then associate these data stores with integrated applications created on the user interface. The newly-architected SecureAuth IdP was launched with minimal features to acquaint you with a new approach in configuring the robust and flexible product. Many tabs on the familiar Web Admin – now called the Classic Web Admin – must still be configured in order to complete the application in version 9.3.

The upcoming software release will provide more robust capabilities to complete your applications in the cloud or on your appliance solely using the New Experience Web Admin user interface.


New Experience Web Admin in v9.3

Supported configuration types

The New Experience user interface lets you configure, save, and edit these integration types:


Where the configuration is made

Equivalent Classic Experience configuration
Active Directory data store integrationUser Data Stores

Data tab:

SQL Server data store directory integrationUser Data Stores

Data tab:

SAML Application integrationApplication Manager

Post Authentication tab:

WS-Federation / WS-Trust application integrationApplication Manager

Post Authentication tab:

Data Store configurations are used by applications created on the New Experience user interface. 

Applications are set to use the default Workflow, Multi-Factor Method, and Adaptive Authentication configuration. Go to tabs on the Classic Experience user interface to modify any of these components.


Classic Experience Web Admin in v9.3

Configuration types not yet supported in the New Experience

Use the Classic Experience user interface to configure, save, and edit the following criteria:

SecureAuth IdP version 9.3 pages you create with any of these components must be built in the Classic Experience:

Data Store


The Workflow defines how the end-user accesses the configured page / resource.

Device recognition methods

User login options

Identity / authentication consumption options

Define any of configuration requirements, if necessary:

Adaptive Authentication

The Adaptive Authentication configuration determines how an end-user's login attempt will be handled, based on defined rules:

Multi-Factor Methods

Configured Multi-Factor Methods define which two-factor methods end-users can select and use to authenticate themselves:

Post Authentication

Post Authentication defines the target resource of the application. Except for SAML and WS-Federation Assertion integrations – which are configured on the New Experience – settings must be made on this tab in the Classic Experience for these types of pages:


Identity Management (IdM)

Certificate Based


Generic (HTTP/OAuth/OpenID/etc)

3rd Party App Integrations



Related topic

New Experience and Classic Experience Web Admin