Single Sign-On Token System for Mobile Hybrid Apps
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Mobile wireless communication devices face inconvenience and network load issues due to repeated authentication prompts across multiple applications, leading to increased fraud risks as each application requires separate authentication, causing users to input credentials multiple times and transmit authentication data unnecessarily.
Innovation Solution
Implementing a Single Sign-On (SSO) system that allows users to authenticate once and automatically authenticate across multiple applications, using an SSO token generated by an SSO server, which is shared among compatible applications to provide access to secure data and services without repeated login requests.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If each application requires separate authentication, then security is maintained, but user convenience deteriorates and network load increases
Solution Approach 1:
The patent introduces an SSO server as an intermediary between applications and authentication systems. The SSO server receives authentication requests from multiple applications, validates user credentials once, and issues authentication tokens that can be reused across different applications. This mediator approach maintains security through centralized validation while improving user convenience by eliminating repeated login prompts.
Solution Approach 2:
The SSO server performs multiple functions: it authenticates users for different applications, issues reusable authentication tokens, and manages session state across applications. This universal authentication service allows a single authentication mechanism to serve multiple applications, reducing the need for application-specific authentication flows and decreasing network traffic.
2Reliability
If authentication data is transmitted to each application's backend server, then each application can verify user credentials, but network resources are overloaded and fraud risk increases
Solution Approach 1:
The patent merges the authentication verification function into a single centralized SSO server that serves all applications. Instead of each application independently verifying credentials against backend servers, all authentication requests are consolidated at the SSO server, which then issues tokens to applications. This combining approach reduces redundant authentication verifications and decreases overall network traffic while maintaining authentication reliability.
Solution Approach 2:
The SSO server creates reusable authentication tokens that copy the authentication state across multiple application sessions. These tokens contain verified user information and can be presented to different applications without re-transmitting the full authentication data, reducing network bandwidth requirements while maintaining verification capability.
3Reliability
If repeated authentication prompts are shown, then each application ensures user authorization, but user frustration increases and authentication efficiency decreases
Solution Approach 1:
The SSO server performs preliminary authentication action by validating user credentials once and issuing an authentication token before the user needs to access multiple applications. This preliminary authentication establishes a reusable authorization state that eliminates the need for repeated authentication prompts across different applications, improving efficiency while maintaining authorization reliability through token validation at each application.
Data Source
AI summary
Single sign on (SSO) functionality is provided across native and hybrid applications executing on a mobile communication device, such that both native and hybrid applications can access authenticated services offered through respective application servers without repeatedly providing authentication credentials. In operation, the mobile device obtains an SSO token from an SSO server providing the SSO functionality, and native applications executing on the mobile device retrieve the SSO token from memory for use in accessing authenticated services. In the case of hybrid applications, an alias is assigned to the mobile device in response to receiving a page request received from the hybrid application. The alias is associated with SSO token of the mobile device in the SSO server, and is used to provide the SSO token directly to the hybrid application from the SSO server such that the hybrid application can use the SSO token for authentication.