Browser Login Information Sharing via SSO Server Mediation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems face challenges in securely sharing account information between devices and browsers, leading to user inconvenience, security vulnerabilities, and increased battery consumption due to repeated login processes and potential exposure of account information.
Innovation Solution
A method involving HTTP communication, generating a random number value, and validating a browser and authentication web server using a user authentication token and timestamp, with an SSO agent managing the process to enhance security and reduce battery consumption.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If account information is transmitted from device to browser via local host, then login convenience is improved, but security vulnerability increases and battery consumption increases
Solution Approach 1:
The patent introduces an authentication web server as an intermediary between the device and browser. Instead of direct communication via local host, the authentication web server mediates the authentication process by receiving authentication information from the device, verifying it, and providing authentication tokens to the browser. This eliminates the security vulnerability of local host transmission while maintaining login convenience.
Solution Approach 2:
The patent extracts the authentication functionality from the device's local host and relocates it to a remote authentication web server. By separating the authentication logic from the device, the system eliminates the security risk associated with local host vulnerabilities while preserving the ability to share account information between device and browser.
2Ease of operation
If local host runs continuously to transmit account information, then login convenience is improved, but battery consumption increases
Solution Approach 1:
Instead of running the local host continuously, the patent implements periodic action by only activating the authentication process when actually needed for login. The authentication web server handles requests on-demand, and the device only transmits authentication information when a login operation is initiated, significantly reducing battery consumption while maintaining login convenience when required.
Solution Approach 2:
By extracting the authentication functionality from the device's continuous operation and relocating it to a remote server, the system eliminates the need for the device to maintain a running local host. The authentication web server handles all authentication requests, allowing the device to remain in low-power state until authentication is actually needed.
3Reliability
If OTP is used for login via browser, then authentication capability is improved, but security vulnerability increases due to network extortion risk
Solution Approach 1:
The authentication web server acts as a trusted intermediary that generates and manages OTPs securely. Instead of the browser directly handling OTP generation (which is vulnerable to network extortion), the authentication web server generates OTPs, transmits them securely to the device for verification, and then provides authentication tokens to the browser. This mediates the authentication process to eliminate network extortion risks while maintaining OTP-based authentication capability.
Data Source
Figure 1
Figure 2(a)~2(c)
Figure 3(a)~3(b)
AI summary
A method of providing login information and an electronic device performing the method are disclosed. A method of providing login information may include sending, from a service web page executed on a browser, a login request to an authentication web page executed on the browser, executing, by the authentication web page, a single sign on (SSO) agent in an electronic device, sending, by the authentication web page, a request for authentication information of a user to the SSO agent, generating, by the SSO agent, a random number and transmitting the random number to the authentication web page, generating an encrypted eigenvalue on an authentication web server based on the random number and transmitting the eigenvalue to the SSO agent, calling, by the SSO agent, an authentication application programming interface (API) server, and transmitting the eigenvalue, validating the eigenvalue on the authentication API server, and receiving, by the SSO agent, a result of the validating from the authentication API server, and transmitting the authentication information to the authentication web server.