Native App Authentication Failover via Code Linking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Native applications face challenges in updating authentication methods, leading to potential authentication failures when they do not support newer security measures, especially when platform-specific APIs are lacking, and users may be unable to access secured resources due to outdated authentication approaches.
Innovation Solution
Implementing code-based linking as a failover method, where a code is generated and used to authenticate both the native application and browser-based applications, allowing users to access accounts even if the native application is not updated to support new authentication factors, using techniques like QR codes, Bluetooth, or NFC for inter-device communication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If native applications use platform-specific authentication APIs, then authentication security is improved, but device compatibility deteriorates when the application is not updated
Solution Approach 1:
The patent introduces a code-based linking mechanism as an intermediary between the native application and the authentication service. When platform-specific APIs are unavailable or outdated, the system generates a code that can be entered through a browser-based interface, which then communicates with the authentication service to complete the authentication process. This intermediary code-based approach bridges the gap between outdated native applications and updated authentication requirements.
2Adaptability or versatility
If native applications are updated to support new authentication factors, then authentication capability is improved, but ease of operation deteriorates due to update requirements
Solution Approach 1:
The patent employs disposable, short-lived authentication codes that can be generated and used without requiring application updates. These codes are temporary and single-use, providing a lightweight solution that bypasses the need for complex application updates while maintaining security. The codes can be entered through simple browser interfaces, preserving user convenience.
3Adaptability or versatility
If code-based linking is implemented as failover, then adaptability is improved, but device complexity increases
Solution Approach 1:
The code-based linking mechanism serves multiple functions: it acts as a primary authentication method when platform APIs are available, serves as a failover when APIs are unavailable, and provides a update-independent authentication path. This universal approach simplifies the overall system architecture by providing a single code-based solution that handles multiple authentication scenarios without requiring separate complex systems for each case.
Data Source
AI summary
Disclosed are various embodiments for providing a native authentication experience with failover. A network service authenticates a first application executed in a computing device in a first instance using one or more authentication factors received via a platform-specific application programming interface that is native to the computing device. After a change to how authentication is performed by the network service, the network service authenticates the first application in a second instance via code-based linking with a second application that is authenticated.