Cross-App User Authentication With Token-Based Data Retrieval
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
There is no convenient way for applications on a smartphone to access data relevant to another app, such as insurance claim data from an insurance app when communicating with a text messaging app.
Innovation Solution
A method involving user authentication in a native mobile application, obtaining an authorization code, storing contextual data via an API, and passing an ID parameter comprising the authorization and retrieval data tokens to a chat application, allowing a customer service provider to retrieve the contextual data using access and retrieval data tokens.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If user authentication is implemented in each application, then data security is improved, but user convenience deteriorates due to repeated authentication requirements
Solution Approach 1:
The system performs preliminary authentication when the user first accesses an application, stores the authentication result (access token) for future use, and automatically retrieves it when the user accesses another application. This eliminates the need for repeated authentication while maintaining security, as the pre-obtained tokens are reused across applications.
Solution Approach 2:
The system creates and uses access tokens that copy the user's authentication credentials. Instead of requiring the user to authenticate repeatedly, the system generates token copies that represent the user's authenticated state and passes these tokens between applications, allowing seamless access while maintaining security verification.
2Adaptability or versatility
If data is shared between applications, then application functionality is improved, but data security deteriorates due to potential unauthorized access
Solution Approach 1:
The system introduces an intermediary authentication mechanism (access tokens and authorization codes) that mediates data sharing between applications. Instead of direct access, applications must obtain and validate tokens through the authentication system, which verifies user permissions and controls data access, enabling functionality while maintaining security boundaries.
Solution Approach 2:
The system changes the state of data access from direct/unrestricted to token-based/restricted by introducing authentication parameters (access tokens, authorization codes, expiration times). These parameter changes control which applications can access which data under what conditions, enabling versatile data sharing while maintaining security through configurable access controls.
3Ease of operation
If authentication tokens are stored for later use, then user convenience is improved by avoiding re-authentication, but security deteriorates due to potential token theft or misuse
Solution Approach 1:
The system uses short-lived access tokens that expire after a certain period or after a single use. Instead of storing permanent authentication credentials, the system generates temporary tokens that are discarded after use or expiration, reducing the security risk of stolen tokens while maintaining user convenience through automatic token management.
Solution Approach 2:
The system implements periodic token expiration and renewal, where access tokens are valid only for specific time periods. This periodic invalidation requires users to re-authenticate after expiration, balancing convenience during the token's valid period with security through time-limited access, while the system automatically manages the renewal process.
Data Source
AI summary
The following relates generally to data retrieval and user authentication. In some embodiments, a user is authenticated in a native mobile application. The native mobile application then obtains an authorization code, and calls an application programming interface (API) to store contextual data about the user. The API then returns, to the native mobile application, a retrieval data token. The native mobile application then launches a chat application via a universal resource identifier (URI), and passes an identification (ID) parameter to the chat application. The chat application then passes the ID parameter to a customer service provider, which then retrieves an access token based upon the authorization code. The customer service provider then retrieves, from the API, the contextual data based upon the: (i) access token, and (ii) retrieval data token.