Uniqkey incident
[Legacy] UniqKey Legacy: Login Process Stalling After Mobile App Approval
Uniqkey experienced a minor incident on August 21, 2024 affecting [Legacy] Uniqkey Extension API and [Legacy] Uniqkey Mobile APP, lasting 1d 3h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Aug 21, 2024, 08:18 AM UTC
We are currently investigating an issue reported by multiple users where the login process stalls after approving the login prompt in the mobile app. This issue primarily affects users on Edge and Firefox browsers, though some reports suggest it may also affect Chrome. Note: We would also like to emphasize that these issues are specific to the Uniqkey Legacy App. Our Uniqkey 2.0 platform remains unaffected and continues to function as expected. Current Findings: - Initial analysis indicates that the issue may be related to the extension’s inability to decrypt data, possibly due to incorrect key pair handling. - Our monitoring tools show stable backend performance, which suggests the issue may not be server-related but could be specific to the extension’s integration with the affected browsers. Next Steps: - We are conducting further tests to isolate whether the issue is specific to certain browser environments or a broader problem across the Legacy Uniqkey Platform. - A technical assessment is underway to determine if this is a product-wide issue on the Legacy Uniqkey Platform. Timeframe: - Start Time: 21/08/2024, 08:25 UTC+2 - We will update with more information as soon as possible Contact Us: If you have any questions or need further assistance, please contact our support team at [email protected].
- monitoring Aug 22, 2024, 06:41 AM UTC
Update: We have resolved the issue that caused the login process to stall after approving the login prompt in the mobile app. Additionally, the Trusted Browser issue has been resolved. Trusted Browser issue: The issue occurred when, after approving a trusted browser in the app, the accounts in the Uniqkey extension were marked as “trusted.” However, when logging into a “trusted” site, Uniqkey still sent an “approve/deny login” request to the mobile app. Resolution: - The problem was traced to the extension’s inability to decrypt data due to incorrect key pair handling in the affected browsers. - A fix has been developed, and an updated version of the extension has been submitted to the Edge, Firefox, and Chrome extension stores. - The latest version is 2.7.1. Please update to the latest version as soon as it becomes available in your preferred extension store. Usually, the extension stores accept the update within hours. We will update this post once all extension stores have accepted our newest version. Next Steps: - We recommend that users update to the latest version of the Uniqkey extension once it becomes available in the extension stores to resolve this issue. The latest version is 2.7.1. - Our team will continue to monitor the situation to ensure the issue remains resolved. Contact Us: If you have any questions or need further assistance, please contact our support team at [email protected].
- resolved Aug 22, 2024, 11:36 AM UTC
We are pleased to inform you that the incident regarding the login process stalling after mobile app approval has been fully resolved. Incident Closure: - All extension stores have been updated, and users should now be able to log in without any issues regarding to this incident after updating the Uniqkey browser extension to the latest version 2.7.1. - The incident is now officially closed. Timeframe: - Start Time: 21/08/2024, 08:25 UTC+2 - Resolution Time: 22/08/2024, 12:48 UTC+2 This issue was specific to the Uniqkey Legacy App. Our Uniqkey 2.0 platform remains unaffected and continues to function as expected. Contact Us: If you have any questions or need further assistance, please contact our support team at [email protected].