Central Manager for Application SSO via Dynamic Code Injection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Single Sign On (SSO) operations for multiple applications require rewriting applications, and existing solutions fail to remotely manage and customize access efficiently, especially for GUI applications like GNOME, which lack standard remote control capabilities and are affected by screen realignment.
Innovation Solution
Implementing a mechanism to access applications externally by intercepting requests, injecting customization code dynamically, and replaying user intentions through a central manager and repository, allowing SSO and remote control without modifying application code, and capturing user intentions rather than specific actions to maintain functionality across screen realignments.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If applications are rewritten to support SSO operations, then SSO capability is achieved, but application development time and complexity increase
Solution Approach 1:
The patent introduces a central manager and customization code as an intermediary layer between the user and applications. The central manager handles SSO operations by injecting customization code into applications dynamically, allowing SSO functionality without modifying the application source code. This mediator approach resolves the contradiction by enabling SSO capability while keeping application development simple.
Solution Approach 2:
The system changes the state of applications by dynamically injecting customization code that modifies runtime parameters and behavior. Instead of rewriting applications, the system alters their execution parameters through injected code that enables SSO operations, thus achieving reliability improvement without increasing development complexity.
2Ease of operation
If applications are rewritten to support remote management, then remote control capability is achieved, but maintenance overhead increases
Solution Approach 1:
The central manager acts as a mediator that enables remote management operations without requiring application modifications. It injects customization code that allows remote control and monitoring capabilities while keeping the original applications unchanged, thus avoiding increased maintenance overhead.
Solution Approach 2:
The system performs preliminary actions by pre-configuring the central manager with templates and customization code that can be dynamically injected into applications. This preliminary preparation enables remote management capability while keeping maintenance simple, as the infrastructure is set up in advance rather than requiring ongoing application modifications.
3Extent of automation
If user actions are recorded for replay, then automation is achieved, but functionality breaks when screen realignment occurs
Solution Approach 1:
The system transitions from static coordinate-based replay to dynamic intention-based replay. Instead of recording fixed screen coordinates that break with realignment, the system captures user intentions and uses the customization code to dynamically determine actions based on current application state, maintaining reliability while preserving automation.
Solution Approach 2:
The customization code injected into applications provides feedback mechanisms that allow the replay system to adapt to screen realignments. By monitoring application state and providing feedback loops, the system can adjust replay actions dynamically based on current conditions rather than relying on fixed recorded coordinates, thus maintaining functionality reliability.
Data Source
AI summary
Apparatus, systems, and methods may operate to send, from a central manager to one or more target machines, an access request associated with at least one application selected from a plurality of applications on the target machines, the access request identifying the target machines, the applications, and access customization code corresponding to the applications; and to send access customization code and a script corresponding to the applications from a central repository to the target machines when the customization code is not resident on the target machines. Further activities may include loading the access customization code as a library on the target machines linked to the applications and replaying recorded user intention input according to a script to supply the input to objects associated with the applications to access and otherwise control the applications. Additional apparatus, systems, and methods are disclosed.