Authentication Microservice Generation for Serverless Functions

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Traditional firewall-based authentication technologies are inefficient for serverless architectures and FaaS, as they are costly to update and do not accommodate the dynamic and specific authentication needs of individual microservices or nodes in virtualized environments.

Innovation Solution

A method and system that uses a machine-learning algorithm to parse computer code, construct an authentication template, and create an authentication microservice for each software unit, allowing for user modification and deployment within the unit, enabling node-level authentication management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional firewall-based authentication is used, then robust protection is provided, but updating authentication settings is costly in terms of ramp-up time and developer effort

Engineering Contradiction:

Improveauthentication protectionVSAvoidramp-up time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent segments authentication management from the centralized firewall to individual function-level authentication microservices. Each microservice handles authentication independently, allowing rapid updates without affecting other services. This segmentation enables parallel development and deployment, dramatically reducing ramp-up time while maintaining robust protection through consistent authentication enforcement across all functions.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The authentication microservices are self-contained and can be independently updated, deployed, and managed. Each microservice automatically handles its own authentication logic based on the specific requirements of its parent function, eliminating the need for manual firewall configuration updates. This self-service capability reduces developer effort and accelerates authentication setting changes.

Inventive Principle:

Principle #25Self-service

2Reliability

If traditional firewall-based authentication is used, then robust protection is provided, but developer effort increases

Engineering Contradiction:

Improveauthentication protectionVSAvoiddeveloper effort

Core Design Contradiction:

ReliabilityVSEase of manufacture

Solution Approach 1:

The authentication microservices automatically generate and manage their own authentication configurations based on function metadata and security requirements. The system self-provisions authentication mechanisms without requiring extensive manual developer intervention, thereby reducing developer effort while maintaining robust protection through automated security policy enforcement.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The patent implements a universal authentication microservice template that can be applied across multiple functions with different authentication needs. This multi-functional approach allows a single standardized authentication framework to serve diverse authentication scenarios, reducing the overall developer effort required to implement and maintain authentication across the entire serverless application portfolio.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Ease of operation

If centralized authentication is used, then simplified management is achieved, but specific authentication needs of individual microservices cannot be met

Engineering Contradiction:

Improveauthentication managementVSAvoidauthentication specificity

Core Design Contradiction:

Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent divides authentication management into segmented, function-specific microservices while maintaining a standardized operational framework. Each microservice is tailored to the specific authentication needs of its parent function, yet all follow consistent deployment and management procedures. This segmentation enables both ease of operation through standardized processes and adaptability through customized authentication logic for each microservice.

Inventive Principle:

Principle #1Segmentation

4Adaptability or versatility

If authentication settings are customized for each node, then specific authentication needs are met, but system complexity increases

Engineering Contradiction:

Improveauthentication specificityVSAvoidsystem complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent uses template-based copying to create authentication microservices. A standardized authentication microservice template is replicated and customized for each function, inheriting common configurations and behaviors. This copying approach allows specific authentication settings for each node while avoiding the complexity of building custom authentication logic from scratch for each service, thereby reducing overall system complexity.

Inventive Principle:

Principle #26Copying

Data Source

PatentUS11468158B2Authentication for functions as a service

Publication Date: 2022.10.11 AT&T INTELLECTUAL PROPERTY I L P

AI summary

A machine-learning algorithm receives code indicative of a software unit and parses the code to extract an authenticating parameter. The machine-learning algorithm constructs an authentication template based on the authenticating parameter and providing the authentication template to a user. The algorithm receives user input from the user responsive to the authentication template and creates an authentication microservice based on the authentication template (and optionally the input). The algorithm links the authentication microservice to the software unit to deploy the authentication microservice within the software unit. The machine-learning algorithm is then modified based on the input.