Token Security Microservice for Unified Governance Platform

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current platforms for accessing multiple intensive computing solutions, such as high performance computing, quantum computations, and artificial intelligence, face challenges in securely and transparently adding or modifying services without disrupting the entire system.

Innovation Solution

A method and system for logging new microservices onto a unified governance platform, utilizing a token security microservice, security repository, and logging module, which enables secure authentication and access to resources without requiring platform shutdown, allowing for the integration of various intensive computing solutions like high performance computing, supervised/unsupervised learning, and quantum computations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a new microservice is added to the unified governance platform, then the platform's functionality and versatility are improved, but the system complexity and security management burden increase

Engineering Contradiction:
Improveplatform functionalityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The platform architecture is segmented into independent microservices, each with specific functions. The token security microservice is separated as a dedicated security component that handles authentication independently from other services. This segmentation allows new microservices to be added without increasing overall system complexity, as each service remains modular and independently manageable.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The token security microservice provides universal security functionality that can be applied to any microservice on the platform. By creating a multi-functional security component that handles authentication, token generation, and verification for all services, the platform avoids the need for separate security implementations for each new microservice, thereby preventing complexity accumulation.

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

2Reliability

If traditional service addition methods are used, then security verification can be performed, but the platform must be stopped and restarted to add new services

Engineering Contradiction:
Improvesecurity verificationVSAvoidservice addition efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The platform implements dynamic service registration and token generation capabilities. New microservices can be added to the platform at runtime without requiring a platform shutdown. The token security microservice dynamically generates authentication tokens for newly registered services, allowing the system to adapt and evolve while maintaining security verification integrity.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The token security microservice performs preliminary security setup and token configuration in advance. By pre-configuring security protocols and token generation mechanisms that are independent of specific services, the platform enables new microservices to be integrated immediately upon registration without requiring platform restarts or complex security reconfiguration.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If multiple intensive computing solutions are integrated into one platform, then access efficiency and unified governance are improved, but the security management and authentication complexity increase

Engineering Contradiction:
Improveaccess efficiencyVSAvoidauthentication complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The token security microservice provides a universal authentication mechanism that works across all intensive computing solutions (HPC, quantum computing, AI/ML platforms) integrated on the platform. This single security component handles authentication for diverse services, maintaining access efficiency while preventing authentication complexity from increasing proportionally with the number of integrated solutions.

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

Solution Approach 2:

The token security microservice acts as an intermediary between various intensive computing solutions and the unified governance platform. It mediates authentication requests by generating and verifying tokens, thereby simplifying security management across multiple solutions while maintaining access efficiency. This intermediary approach prevents direct complex interactions between diverse computing solutions.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11665152B2Method and system for discovering and logging new microservices for a platform for unified governance of a plurality of intensive computing solutions
Publication Date: 2023.05.30 BULL SA
  • US11665152B2 patent drawing
  • US11665152B2 patent drawing
  • US11665152B2 patent drawing

AI summary

A method (800) for logging microservices in a platform for unified governance of a plurality of intensive computing solutions (70) comprising: a proxy microservice (20), a token security microservice (30), at least one security repository (35,36,37), a logging module (90), a service register (91), and comprising the steps of:Reception (820) of a join request from a new microservice (60),Verification (830) of the unique identifier of the new microservice (IDMS),Generation (840) of an authentication token and transmission to the new microservice,Reception (850) of a logging request from a new microservice, comprising data that providesaccess to the resources of the new microservice and the generated authentication token,Verification (860) of the authentication token with the token security microservice (30),Logging (870), when the authentication token is validated, data that provides access to the resources of the new microservice on the service register (91).