Safewhere Identify 5.16 - Known issues

This document summarizes known issues and workarounds where available.

• Identify's Data Protection code uses the EntityID as the application discriminator, influencing the encryption process. When you modify this EntityID on the Settings page, data encrypted with the old EntityID cannot be decrypted using the new one. Consequently, you might encounter the error message The payload was invalid.

  • Workaround: To address this issue, simply close your currently open browser and then reopen it. Additionally, changing the EntityID, if desired, should be the first step after creating a new tenant.

• Issue #107110 [Chrome][Firefox][WebAuthn] The user can register or authenticate WebAuthn even after the request times out (the countdown is over)

  • Root cause: The response time (in seconds) required for interacting with WebAuthn-compatible devices during registration or authentication on Chrome and Firefox browsers is currently inconsistent due to recent updates in both browsers.

    • Specifically, Chrome browsers require setting the Prompt timeout value to a minimum of 180,000 milliseconds (3 minutes).
    • Meanwhile, on Firefox browsers, the Prompt timeout functionality is not working.

  • Workaround: For Chrome browsers, the suggested workaround involves setting the Prompt timeout value to 180 seconds or more. As for Firefox browsers, no workaround is currently available, and there is an expectation that Firefox will address this issue in future versions.