Cross-Domain Authentication Using Confirmation Codes Without Cookies
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Redirecting a user from a storefront to a payment processing portal across different network domains typically requires third-party cookies, which may not be supported by all browsers or may be opted out by users, leading to authentication challenges.
Innovation Solution
A server in a first network domain facilitates user login or authentication based on information received from a second network domain without using third-party cookies, utilizing a unique identifier to transmit a confirmation code to the user device for completing the login process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If third-party cookies are used for authentication across network domains, then user authentication can be maintained, but browser compatibility and user privacy preferences cause authentication failures
Solution Approach 1:
The patent introduces a domain indicator value (DIV) as an intermediary mechanism to replace third-party cookies for cross-domain authentication. The DIV is stored in the browser and exchanged between domains through URL parameters, enabling reliable authentication without depending on third-party cookie support. This intermediary approach resolves the contradiction by maintaining authentication reliability while being compatible with all browsers regardless of their third-party cookie settings.
Solution Approach 2:
The patent extracts the authentication state from the third-party cookie mechanism and implements it through a separate, independent system using domain indicator values. By separating the authentication state storage from the cookie dependency, the solution removes the restriction imposed by browser cookie policies while maintaining cross-domain authentication functionality.
2Object-affected harmful factors
If users opt out of third-party cookies, then privacy is protected, but authentication across domains becomes challenging
Solution Approach 1:
The domain indicator value serves as a privacy-friendly intermediary that achieves authentication without requiring third-party cookies. The DIV is implemented in a way that respects user privacy preferences while still enabling the necessary authentication functionality across domains.
3Adaptability or versatility
If redirecting between network domains is implemented, then payment processing can be separated, but authentication state cannot be maintained without third-party cookies
Solution Approach 1:
The patent uses the domain indicator value as an intermediary to maintain authentication state across domain redirects. The DIV is passed through URL parameters during redirection, allowing the payment processing portal to verify user identity without third-party cookies, thus enabling service separation while maintaining authentication reliability.
Solution Approach 2:
The patent performs preliminary actions by storing the domain indicator value in the browser before redirection occurs. This pre-stored DIV is then available for verification at the payment processing portal, enabling seamless authentication state maintenance across domain boundaries without requiring third-party cookies.
Data Source
AI summary
A server of a first network domain receives an indication container object created in a second network domain. The server identifies, based on the indication container object, a unique identifier, where the unique identifier allows initiation of logging into an account. The server transmits a confirmation code to a user device that is identified based on the unique identifier. Transmitting the confirmation code allows completion of login to the account.