Microservices Identity Management for Multi-Tenant Security

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current identity management systems in cloud environments face challenges in providing secure access across diverse devices and user types, including unauthorized access, account hijacking, and inconsistent security between on-premise and cloud environments, particularly when managing access for employees, customers, and partners.

Innovation Solution

A microservices-based architecture for cloud identity and access management that implements multi-tenant identity and data security, supporting secure access across hybrid cloud deployments, integrating with both cloud and on-premise systems, and providing unified security controls through APIs, Single Sign-On (SSO), and adaptive authentication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional identity management systems are used in cloud environments, then security control is maintained, but security consistency across diverse devices and user types deteriorates

Engineering Contradiction:
Improvesecurity controlVSAvoidsecurity consistency across devices
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The identity management system is segmented into independent microservices, each handling specific identity management functions. This segmentation allows the system to maintain core security controls while adapting to diverse devices and user types through specialized service components that can be independently configured and deployed.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The microservices architecture implements universal identity management capabilities that can serve multiple devices, user types, and cloud environments through a common framework. The system provides multi-functional support for authentication, authorization, and security policies across hybrid cloud, public cloud, and on-premise environments through standardized service interfaces.

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

2Adaptability or versatility

If microservices architecture is implemented for identity management, then adaptability and scalability are improved, but system complexity increases

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

Solution Approach 1:

The system is divided into independent microservices that can be developed, deployed, and scaled separately. Each microservice encapsulates specific functionality, reducing the complexity burden on individual components while enabling the overall system to achieve high scalability and adaptability through modular architecture.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If multi-tenant identity management is implemented, then service coverage is improved, but security management complexity increases

Engineering Contradiction:
Improveservice coverageVSAvoidsecurity management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system implements local quality by providing customized security policies and authentication mechanisms tailored to each tenant's specific requirements while maintaining a unified multi-tenant architecture. Each tenant can have differentiated security configurations, user management policies, and access controls appropriate to their organizational needs.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS10200358B2Microservices based multi-tenant identity and data security management cloud service
Publication Date: 2019.02.05 ORACLE INT CORP
  • US10200358B2 patent drawing
  • US10200358B2 patent drawing
  • US10200358B2 patent drawing

AI summary

A system provides cloud-based identity and access management. The system receives a request for performing an identity management service, where the request includes a call to an application programming interface (“API”) that identifies the identity management service and a microservice configured to perform the identity management service. The system authenticates the request, accesses the microservice, and performs the identity management service by the microservice.