Skip to main content

Known issues

Latest release version: 19.07.01

The following are known issues in the SecureAuth Identity Platform release 19.07 and later. The Workaround column indicates whether there is a workaround until a fix can be applied in a later release.

[ 19.07 known issues ] [ 19.07.01 known issues ]

19.07 known issues

Ref ID	Description	Workaround
IDP-5687	Knowledge based questions and answer entries are missing from the Web.config file. This occurs when you set the Profile Connection Settings to No Data Store, saving it and then going back in and selecting a data store.	Go to the Web Configuration Editor and add the fields back in.
IDP-5838	After upgrading to 9.3, the SecureAuth0 Verbiage Editor cannot update resource.dll file.	Start and stop the SecureAuth Cloud Transport Service.
IDP-6515	TRX logging enabled on data realms creates redundant traffic.	For a workaround, contact Support.
IDP-7043	Login counts are duplicated on the Dashboard.	No workaround. Will be fixed in a later release.
IDP-7045	Data store counts are not reflected on the Dashboard.	No workaround. Will be fixed in a later release.
IDP-7431	After upgrading from SecureAuth IdP 9.3 to Identity Platform 19.07, new application integrations are created to use the 2016 Light theme instead of the new default 2019 theme.	As a workaround for all new application integrations to use the 2019 theme by default, create a template realm and set the 2019 default theme for new realms.
IDP-7495	This issue exists in realms that have the following conditions: Application integration created in the New Experience Policy assigned to the application integration has Text Message confirmation link AND Email confirmation links selected as multi-factor authentication (MFA) methods 2016 Light theme selected on the Overview tab (legacy realm) If you have realms with the above conditions, the PIN and KBQ methods do not display on the One-Time Registration Code delivery method page to end users.	Option 1: Change the application realm to use the 2019 Theme. Option 2: If you must keep the 2016 Light theme, do the following: In the affected application realm, go to the Multi-Factor Methods tab (Classic Experience), and scroll down to the Multi-Factor Method Order section. Reorder the multi-factor method by moving one up or down. Save your changes.

19.07.01 known issues

Ref ID	Description	Workaround
IDP-7589	A workflow is initially set up to use Username \| Second Factor. Then, when a policy assigned to an application changes the default workflow to use any Valid Persistent workflow, the Public/Private mode option incorrectly displays to the end user instead of the Private only option.	As a workaround, in to the Classic IdP Web Admin, locate the affected realm and click Save.
IDP-7595	Unable to receive certification on the Revoke Certification page.	As a workaround, update the web.config file from the Tools menu.
IDP-7592	On the Portal Page Builder page, when you change the Portal Page Authorization from one form of authorization to "Not Available", all of the realm check boxes are not enabled for selection.	As a workaround, select any option other than "Not Available", then select the "Not Available" option, and click Save.
IDP-7565	This issue exists in realms that have the following conditions: Application integration created in the New Experience Policy assigned to the application integration has KBQ / KBA and/or PIN enabled as multi-factor authentication (MFA) methods 2016 Light theme selected on the Overview tab (legacy realm) If you have realms with the above conditions, the PIN and KBQ methods do not display on the One-Time Registration Code delivery method page to end users.	Option 1: Change the application realm to use the 2019 Theme. Option 2: If you must keep the 2016 Light theme, do the following: In the affected application realm, go to the Multi-Factor Methods tab (Classic Experience), and scroll down to the Multi-Factor Method Order section. Reorder the multi-factor method by moving one up or down. Save your changes.
IDP-7569	On the Multi-Factor App Enrollment realm, when OATH Seed (Single) is selected for mobile app enrollment, the Time-based Passcode does not display on the pick list to the end user to enroll in the Authenticate app.	Option 1: The recommended workaround option is in the App Enrollment realm, use the OATH Token option instead of OATH Seed. Option 2: In order to use the OATH Seed option, both the OATH Seed and OATH Token must be mapped in the Directory Property mapping in a legacy realm in order for the Identity Platform to convert the Authenticate App (OATH Seed) to a token. See the KB article: How to convert an OATH Seed to OATH Token. And then use a workflow that includes second factor (for example, Username \| Second Factor \| Password) for the default workflow login and enable Time-based Passcode in the Multi-Factor Methods configuration. Once the end user has successfully authenticated with Passcode in the legacy realm, the Passcode option can be used in any realm.
IDP-7597	Cloud data store latency issue with service account update.	No workaround. Will be fixed in a later release.
IDP-7618	Global Aux ID fields do not display on the Data tab in the on-prem version.	Issue to be resolved in a hotfix release.
IDP-8204	In the Identity Platform 19.07 using a cloud instance with the SecureAuth Connector, some sites receive a 504 gateway timeout error when going to post authentication.	Install version 1.1.4 of the SecureAuth Connector. It is available on the Identity Platform Data Stores page, under the Connector tab, at the bottom of the screen. Perform a service account login to the on-prem data store to access the Writable field settings. Set to Writable all properties you will map to the SecureAuth Connector. View a table that shows where the available data store profile properties are stored for cloud deployment. SecureAuth development is working to remove this requirement in a future release.

In this section:

Would you like to provide feedback? Just click here to suggest edits.