Multi-Tenant Identity Management Microservices Architecture

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current identity management systems face challenges in providing secure access to cloud-based applications across diverse devices and user types, with inconsistencies in security between on-premise and cloud environments leading to potential security breaches, especially when managing access for employees, customers, and partners.

Innovation Solution

The implementation of a multi-tenant, cloud-scale identity and access management platform using a microservices architecture, which includes a 'Cloud Gate' that secures access to APIs, provides unified security controls, and supports hybrid cloud deployments, ensuring secure access across various channels and environments.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a multi-tenant identity management system is implemented to provide unified security controls across cloud-based applications, then security consistency and access control are improved, but system complexity and deployment challenges increase

Engineering Contradiction:
Improvesecurity consistencyVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The identity management system is segmented into multiple independent microservices, each handling specific security functions such as authentication, authorization, and identity provisioning. This modular architecture allows the system to maintain security consistency across multiple tenants while reducing overall system complexity through independent deployment and management of each service component.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements a universal identity management platform that serves multiple tenants and applications through a common set of security controls and policies. This multi-functional approach enables a single system to provide consistent security across diverse cloud-based applications while avoiding the complexity of implementing separate security systems for each tenant.

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

2Reliability

If access control policies are enforced across diverse devices and user types in cloud environments, then unauthorized access is prevented, but ease of operation and user experience deteriorate

Engineering Contradiction:
Improveaccess securityVSAvoiduser experience
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The access control system dynamically adapts security policies based on user context, device type, and application requirements. This dynamic approach allows the system to enforce appropriate security measures for each access scenario while maintaining ease of operation for legitimate users, as the security controls automatically adjust rather than applying uniform restrictions.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system implements feedback mechanisms that monitor access patterns and user behavior to continuously optimize security policies. By analyzing access requests and adjusting policies based on observed patterns, the system maintains strong security controls while improving ease of operation for approved users through automated decision-making that reduces manual intervention.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11088993B2Policy enforcement point for a multi-tenant identity and data security management cloud service
Publication Date: 2021.08.10 ORACLE INT CORP
  • US11088993B2 patent drawing
  • US11088993B2 patent drawing
  • US11088993B2 patent drawing

AI summary

An embodiment controls access to a resource, the access controlled by a multi-tenant system. Embodiments receive, at a web server, a request for the resource from a user via a web browser, the request including a Uniform Resource Locator (“URL”) associated with the resource and an identity of a tenant corresponding to the user. Embodiments determine an access policy for authenticating the user that is associated with the resource, the access policy based in part on the identity of the tenant. Embodiments then authenticate the user based on the determined access policy.