Authenticated Application Direct Access to Embedded Links
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Embedded hyperlinks often trigger extensive authorization processes, disrupting user experience and requiring additional computing resources, due to security concerns and the need for separate authentication steps.
Innovation Solution
Utilizing authenticated applications as trusted proxies to provide direct access to objects associated with embedded links, eliminating the need for a separate authorization process by verifying authorization within the authenticated applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If separate authorization process is implemented for embedded hyperlinks, then security is improved, but user experience and access speed deteriorate
Solution Approach 1:
The system performs authorization checks in advance by embedding authorization tokens within the hyperlink structure. When a user clicks a hyperlink, the authorization has already been verified server-side before the link was generated, eliminating the need for additional authorization steps at access time. This preliminary action maintains security while enabling seamless user experience.
Solution Approach 2:
The patent introduces an intermediary authorization token that acts as a mediator between the user and the protected resource. The token encapsulates authorization information and is transmitted with the hyperlink request, allowing the system to verify authorization without requiring the user to undergo separate authentication processes. This intermediary mechanism resolves the contradiction by maintaining security verification while streamlining user access.
2Reliability
If separate authorization process is implemented for embedded hyperlinks, then security is improved, but computing resource usage increases
Solution Approach 1:
Authorization computations are performed in advance when the hyperlink is generated, rather than being repeated each time the link is accessed. The authorization token is computed once and cached, significantly reducing the computing resources required at access time. This preliminary computation maintains security verification while minimizing ongoing resource consumption.
Solution Approach 2:
The system creates a copy of the authorization information in the form of a token that can be reused multiple times without requiring re-computation of the full authorization process. This token copying mechanism maintains security by preserving the original authorization decision while reducing the computational overhead of repeated verification, thereby lowering energy and resource usage.
Data Source
AI summary
Direct access to embedded links via an authenticated application is described. In an example, a first user interface can be presented via a web browser of a computing device, wherein the first user interface includes an actuation mechanism corresponding to an object associated with a platform, and wherein the computing device is associated with an application associated with the platform. In at least one example, an indication of an interaction with the actuation mechanism can be received and based at least in part on (i) receiving the indication of the interaction with the actuation mechanism and (ii) a determination that the application is associated with an active authentication session, the object can be presented via a second user interface presented via the application. As such, direct access to the object can be provided via the authenticated application.