Secure Session Handoff Between Native Apps and Mobile Browsers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for navigating between native applications and mobile internet browsers are inconvenient due to insecure connections, requiring manual reauthentication and interrupting user sessions, especially when sensitive information is involved.
Innovation Solution
A system and method that authenticate users once, generate and manage tokens to enable secure session persistence between native applications and mobile internet browsers, using a server with token management and authentication services to verify identities and grant access without manual reauthentication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the native application directs the internet browser to call the web application, then access to the digital feature is provided on the mobile device, but the connection is insecure and requires manual reauthentication
Solution Approach 1:
The patent introduces an intermediary authentication system that mediates between the native application and web application. The server acts as a trusted intermediary that issues authentication tokens to the native application, which are then passed to the web application through the internet browser. This intermediary layer enables secure communication over the inherently insecure browser connection without requiring manual reauthentication, resolving the contradiction between adaptability and reliability.
2Reliability
If manual reauthentication is required via the internet browser, then information security is maintained, but user convenience is degraded and user session is interrupted
Solution Approach 1:
The patent implements preliminary authentication where the user's identity is verified once in the native application before navigating to the web application. The authentication token is issued in advance and stored securely, allowing the user to bypass reauthentication when accessing the web application. This preliminary action maintains information security while eliminating the need for manual reauthentication, thereby preserving user convenience and session continuity.
3Ease of operation
If the native application uses an insecure connection to the internet browser, then ease of navigation is improved, but security of sensitive information is compromised
Solution Approach 1:
The patent introduces an intermediary authentication token system that protects sensitive information during navigation through the insecure browser connection. Instead of transmitting sensitive data directly, the system uses authenticated tokens that verify user identity without exposing sensitive information. This intermediary mechanism maintains navigation ease while mitigating security risks associated with insecure connections.
Solution Approach 2:
The patent creates a secure copy of authentication credentials in the form of authentication tokens. Rather than transmitting actual sensitive information (passwords, personal data) over the insecure connection, the system transmits token copies that represent authenticated user identity. These tokens can be safely transmitted through the insecure browser connection while maintaining security, as they do not contain actual sensitive information that could be compromised.
Data Source
AI summary
A system and method for enabling user session persistence between a native application and a mobile internet browser on a mobile device. The method includes authenticating a use of the native application and issuing an authentication token to the native application. The method also includes receiving from the native application the authentication token in connection with a destination address and obtaining first identifying data regarding the mobile device. The method further includes generating a key; associating the key, the authentication token, the destination address, and the first identifying data regarding the mobile device together in a database; encrypting the key to generate an encrypted key; and transmitting the encrypted key to the native application. The native application passes the encrypted key and the client key to the internet browser. The method includes receiving from the mobile internet browser the encrypted key; obtaining second identifying data in connection with the encrypted key received; decrypting the encrypted key to generate a decrypted key; locating the authentication token, the destination address, and the first identifying data within the database using the decrypted key; and confirming that the mobile internet browser is executing on the mobile device based at least in part on a comparison of the first identifying data and the second identifying data. If the mobile internet browser is confirmed, it is granted access to the destination address, which may include a feature implemented on a web application.