Dynamic Code Injection for Stale Session Termination
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing computing environments face challenges in efficiently managing and securing network resources, particularly due to the accumulation of stale computing sessions that consume excess resources and pose security risks, as conventional methods like short session timeouts can be problematic for users and resource utilization.
Innovation Solution
Implementing a method to dynamically inject code into response messages in a computing environment, allowing for automatic execution by client-side programs to detect and terminate stale sessions and secure Single Sign On (SSO) cookies using Time-based One Time Passwords (TOTPs), thereby enhancing security and resource management without requiring manual installation of plugins.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a short session timeout interval is used to quickly expire inactive sessions, then the accumulation of stale sessions is reduced, but computing resources are still consumed before sessions are timed out and user convenience deteriorates
Solution Approach 1:
The system performs preliminary actions by injecting client-side code that proactively detects browser-close events and immediately notifies the session server to terminate sessions. This prevents the accumulation of stale sessions before they can consume excessive computing resources, eliminating the need for short timeout intervals and their associated drawbacks.
2Productivity
If code injection is implemented to detect browser-close events and terminate sessions, then stale session accumulation is eliminated, but system complexity increases
Solution Approach 1:
The system introduces an intermediary mechanism where a policy enforcement point (PEP) acts as a mediator between the session server and client applications. The PEP intercepts communication, injects necessary client-side code into response messages, and coordinates session termination events. This intermediary approach manages the complexity by centralizing the code injection logic and providing a structured interface between components.
3Reliability
If manual plugin installation is required to secure sessions, then security functionality can be implemented, but ease of operation deteriorates
Solution Approach 1:
The system implements self-service by automatically injecting the necessary security code into client applications through the policy enforcement point. The client application receives the security functionality embedded in response messages without requiring users to manually install or configure plugins. The code is automatically executed when the application processes the intercepted messages, providing security as a seamless service.
Data Source
AI summary
A client request message is received at a policy enforcement system from a client-side application intended for a server-side application. The client request message is forwarded to a server-side application. An application response message from the server-side application is intercepted at the policy enforcement system in response to the client request message, resulting in an intercepted application response message. The intercepted application response message is analyzed in view of context information and a network policy. Code to inject into the intercepted application response message is determined based on the analyzing. The code has instructions for eliminating accumulation of stale computing sessions. The code is injected into the intercepted application response message, resulting in a modified message. The modified message is forwarded to the client-side application for automatically executing the instructions on the client-side application.