Authentication via Separate Webpage for Pop-up Blocked Browsers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Certain browser applications, such as those on smartphones or other mobile devices, are unable to present pop-up windows simultaneously with webpages, hindering the authentication process for transactions, as they redirect users to separate webpages, thereby preventing the exchange of authentication information with the website.
Innovation Solution
Implementing a method where the user interface for authentication is presented as a separate webpage instead of a pop-up window, allowing the browser application to determine and store website information, and upon successful authentication, an access token is generated and included in the Uniform Resource Identifier (URI) to authorize the transaction, enabling the user to complete transactions even without pop-up window capabilities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a pop-up window is used for authentication, then the authentication context can be determined and authorization can be provided to the website, but browser applications that cannot present pop-up windows are unable to authenticate transactions
Solution Approach 1:
The authentication process is segmented into two separate webpages: the first webpage displays the original website content, and the second webpage handles authentication. This segmentation allows the authentication function to be separated from the website browsing function, enabling authentication in browsers that cannot present pop-up windows by using a separate page context instead of a window context.
Solution Approach 2:
A server acts as an intermediary between the user's browser application and the authentication system. The server receives requests from the first webpage, determines authentication status, and provides authorization data back to the webpage, enabling authentication without requiring the browser to present a pop-up window.
2Ease of operation
If a pop-up window is presented for authentication, then authentication information can be exchanged with the website, but the user interface becomes complex and may not be supported by all browser applications
Solution Approach 1:
The authentication interface is segmented into a separate second webpage rather than being embedded in a pop-up window. This simplifies the user interface structure by using standard webpage navigation instead of complex window-based interactions, making it compatible with all browser applications including mobile browsers.
Solution Approach 2:
Instead of presenting authentication within the same window context as the website (pop-up approach), the system inverts the approach by using a completely separate webpage context for authentication. This reversal of the traditional pop-up pattern simplifies the interface and eliminates compatibility issues with browsers that block or cannot present pop-up windows.
3Adaptability or versatility
If authentication is performed using a separate webpage instead of pop-up, then compatibility with all browser applications is achieved, but the process of determining and storing website information is required
Solution Approach 1:
The server performs preliminary action by determining the website information (such as the Uniform Resource Identifier) associated with the first webpage before the authentication process begins. This pre-determined website information is stored and later used to verify that authorization data is provided to the correct website, eliminating the need for complex real-time information determination during authentication.
Solution Approach 2:
The server serves as an intermediary that handles the complex tasks of determining and storing website information. By centralizing this information management function in the server, the system avoids the complexity of implementing similar logic in the browser application, maintaining simplicity on the client side while achieving full compatibility.
Data Source
AI summary
A system facilitates authentication in situations where a pop-up window fails or is disallowed. If a browser application accessing a first webpage is not capable of presenting pop-up windows and redirects a user to a separate webpage for collecting information, the browser application, the absence of a JavaScript object indicating the pop-up window, or the inability to exchange data with a computing device associated with the first webpage is determined. In such a case, if valid information is received from the user, authorization data is provided to the computing device in the form of text included in a Uniform Resource Identifier (URI) for the first webpage. As a result, transactions may be authorized when a browser application is not capable of presenting pop-up windows.