Safewhere Identify 5.15 - Known issues
This document summarizes known issues and workarounds where available.
- We made numerous changes related to indices in version 5.15. We strongly recommend that you use the Diagnostics and monitoring tool to check the data size of your Identify instances' databases first and perform the necessary data cleanup before upgrading your Identify instances to version 5.15.
- Issue #101766: Encounter
Registration process is either timeout or has been canceled
when performing the onboard/authenticate WebAuthn on the latest version of the Chrome browser.- Workaround: This issue may occur when the SSL certificate on the Identify instance is not valid, such as when using a self-signed SSL certificate. To resolve it, apply a valid SSL certificate to the Identify instance.
- Issue #102222 [IC] Cannot create an Identify instance using Windows authentication when the applied domain credentials' password contains a " (double quote) character.
- Workaround: Reset the domain credentials' password.
- Issue #102343 The Email/SMS claim type shows empty on its dropdown list of the OTP connection.
- Workaround: This issue can occur when the applied claim type was accidentally deleted from the claims list. To resolve it, recreate the claim types or select a new claim.
- The key name information is not detected when uploading SAML 2.0 metadata via scheduled metadata monitoring jobs.
- Workaround: You can reupload metadata either by a metadata file or metadata URI when modifying SAML 2.0 Identity provider/application.