What's New - Verified 3.12.2 Release

This document provides additional details on recently introduced features, tips, limitations, and corrections, and it serves as a supplement to the online help and publications. For comprehensive product documentation and further guidance on using authID.ai Version 3.12.2, please visit the authID.ai Information Center.

We are excited to announce that on Thursday, September 12th, 2024, our authentication software, Verified, will receive a series of minor updates designed to enhance its functionality. The update will take place between 4:30 and 5:00 PM ET, and there will be a 15-minute window of downtime. During this window, users will not be able to log into the identity portal. However, users who are already logged into the portal prior to the update will remain logged in.

Updated Components

  • Identity Deduplication Service
  • Verified
  • Open Identity Connect (OIDC) Service

What's New

  1. Product Enhancements:

    • Performance Enhancements: We have addressed performance delays that were affecting the processing of selfie images post-submission. This update results in a smoother and more efficient user experience.
    • Search API Enablement: The recent update to the Search API now supports incorporating images captured during the Proof process. This advancement reduces the number of API calls and data submissions needed, leading to noticeable improvements in performance and operational efficiency.
  2. Critical Defect Resolutions:

    • White Page During OIDC Authentication (Outlook): Resolved an issue where users encountered a white page while attempting to authenticate via Outlook using an OIDC connection.
    • QR Code Scanner Silhouette: Fixed the display of an unnecessary document silhouette during QR code scanning.
    • Deduplication Error (500): Fixed an issue that triggered a 500 error when no user was found during the deduplication process. The system now returns an empty result as expected.
    • Deduplication Error (409) During Proof Transactions: Fixed the issue where a 409 error occurred during proof transactions. A 200-success code is now returned for these cases.
    • Pending Status with Expired/Rejection Error (409): Resolved an issue causing a 409 error alongside a pending status for expired or rejected transactions. The system now correctly displays the 409 error with appropriate expired or rejected messages.

If you have any questions regarding the changes, please get in touch with us at [email protected].