Authentication Microservice Edge Proxy Cloud Security

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud services face challenges in ensuring security and privacy due to their high accessibility, making them vulnerable to malicious accesses and cyberattacks, as existing architectures often integrate authentication functionality in a monolithic manner, leading to complexity, limited scalability, and resource inefficiency.

Innovation Solution

Implementing an independent authentication microservice executed by edge proxy servers that forwards login requests to a login service for credential verification, creates session tokens, and authenticates subsequent requests, while also routing requests based on geographical information to ensure secure and efficient access across multiple regions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If authentication functionality is integrated in a monolithic manner, then the system structure is simpler, but the scalability and resource efficiency are limited

Engineering Contradiction:
Improvesystem structureVSAvoidscalability
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The authentication functionality is segmented from the monolithic system into an independent authentication microservice. This microservice is deployed as a separate container that can be independently scaled, updated, and managed. The segmentation allows the authentication component to be replicated across multiple instances to handle increased load, thereby improving scalability without complicating the overall system structure.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The authentication functionality is extracted from the main cloud service system into a standalone authentication microservice. This extracted component communicates with the main system through well-defined interfaces, allowing it to be developed, deployed, and scaled independently. The extraction enables resource-efficient authentication processing while maintaining system simplicity through clear separation of concerns.

Inventive Principle:
Principle #2Taking out (Extraction)

2Device complexity

If authentication functionality is integrated in a monolithic manner, then the system structure is simpler, but the resource efficiency is limited

Engineering Contradiction:
Improvesystem structureVSAvoidresource efficiency
Core Design Contradiction:
Device complexityVSUse of energy by moving object

Solution Approach 1:

By segmenting authentication into a separate microservice, resources can be allocated more efficiently. The authentication microservice can be sized appropriately for its specific workload and can be scaled independently from other system components. This prevents over-provisioning of resources and improves overall resource efficiency while maintaining a manageable system structure through containerization.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The authentication microservice is designed as a universal component that can serve multiple applications and services within the cloud infrastructure. By consolidating authentication functionality into a single reusable microservice, the system avoids duplicating authentication logic across multiple services, thereby improving resource efficiency through shared infrastructure while maintaining system simplicity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If authentication functionality is isolated in an independent microservice, then the scalability is improved, but the device complexity increases

Engineering Contradiction:
ImprovescalabilityVSAvoidsystem structure
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

An edge proxy server is introduced as an intermediary component that manages communication between the main system and the independent authentication microservice. The proxy server handles request routing, load balancing, and protocol translation, thereby simplifying the interaction complexity. This allows the authentication microservice to be scaled independently while the proxy manages the complexity of distributed communication, achieving scalability without proportionally increasing overall system complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If authentication functionality is isolated in an independent microservice, then the robustness is improved, but the device complexity increases

Engineering Contradiction:
ImproverobustnessVSAvoidsystem structure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The edge proxy server acts as a protective intermediary between the main system and the authentication microservice. It implements load balancing to distribute traffic across multiple authentication instances, preventing any single point of failure from bringing down the entire system. The proxy also handles health checks and can route traffic around failed components, thereby improving robustness while managing system complexity through a standardized interface layer.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The authentication microservice is deployed with local redundancy, where multiple instances of the authentication service are distributed across different physical or virtual locations. Each instance is self-contained and can operate independently. This local quality approach ensures that if one instance fails, others can continue to handle authentication requests, improving robustness without requiring complex centralized failover mechanisms.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS11606359B1Cloud service authentication microservice
Publication Date: 2023.03.14 MONDAY COM LTD
  • US11606359B1 patent drawing
  • US11606359B1 patent drawing
  • US11606359B1 patent drawing

AI summary

A method of authenticating requests to a cloud service, comprising using one or more edge proxy servers of a container execution system facilitating a cloud service to execute an authentication microservice configured for forwarding, to a login service, each login request received by the edge proxy server, via one or more network, from one or more client devices used by respective users to establish sessions with application(s) executed by application server(s) of the container execution system wherein the login service is configured to authenticate the respective user based on credentials extracted from the login request and create one or more session tokens transmitted to the one or more client device, extracting the session token(s) from each subsequent request received by the edge proxy server from the one or more client devices pertaining to the respective sessions, and authenticating the respective subsequent request by verifying the session token(s).