UI Session Cache for Microservice Authentication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current authentication mechanisms in microservice architectures, particularly at the frontend, are inadequate, as they lack robust security measures, making them vulnerable to malicious activities.
Innovation Solution
A multi-tenant computing system employs a stateless UI session token-based authentication mechanism, where the UI session token is cached with session identifiers and authentication credentials, allowing only authorized access to backend services, and invalidating cache entries based on an expiry policy.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional authentication mechanisms are used in microservice frontend, then ease of operation is maintained, but security is insufficient and vulnerable to malicious activities
Solution Approach 1:
The patent introduces a UI session cache as an intermediary component between the frontend and backend services. This cache stores authentication credentials and session information, acting as a mediator that enhances security without requiring complex authentication logic in the frontend code. The cache validates and manages session tokens, providing a security layer that is transparent to end users.
Solution Approach 2:
The system performs preliminary authentication and credential validation by storing verified authentication credentials in the UI session cache before actual service access occurs. This preliminary action ensures that security checks are completed in advance, allowing the frontend to operate with simplified token-based access while maintaining strong security validation.
2Reliability
If user information is exposed outside the system for authentication purposes, then ease of operation is improved, but security is compromised and user information may be vulnerable to malicious activities
Solution Approach 1:
The patent extracts sensitive user information and authentication credentials from the frontend application and stores them securely in the UI session cache. This extraction removes vulnerable data from the exposed frontend environment while maintaining authentication functionality through token references, thereby securing user information without significantly increasing system complexity.
Solution Approach 2:
The system creates and uses session tokens as copies or representations of user authentication state, rather than exposing actual user credentials. These tokens serve as secure placeholders that enable authentication operations without revealing sensitive user information, balancing security requirements with operational simplicity.
3Productivity
If session tokens are cached with authentication credentials, then authentication speed is improved, but security risk increases if cache is not properly managed
Solution Approach 1:
The patent implements periodic cache invalidation and session expiration mechanisms. The UI session cache automatically invalidates stored credentials after predetermined time periods or upon detecting suspicious activity. This periodic security action maintains fast authentication for valid sessions while systematically eliminating security risks from cached data, balancing speed and security.
Solution Approach 2:
The system incorporates feedback mechanisms that monitor cache usage and session validity. When authentication attempts are made, the system provides feedback about session status and validates cache entries. This feedback loop enables the system to maintain cached credentials for performance while actively detecting and responding to potential security threats through continuous validation and invalidation protocols.
Data Source
AI summary
Systems and methods providing authentication in a microservice system. In some embodiments, the method comprises receiving, from the user interface application, a user interface response corresponding to the user interface request; and sending the user interface response to the client computer. Some embodiments comprise when no cache entry corresponding to the user interface session token is present in the user interface session cache, directing the user interface request to a login service. Some embodiments comprise when the login service receives valid login credentials from the client computer, sending a new user interface session token to the client computer. Some embodiments comprise invalidating the cache entries in the user interface session cache according to a cache expiry policy; and determining whether the cache entry corresponding to the particular user interface session token is valid. In some embodiments, the user interface request session token consists of a single value.