Identity Mapping System Resolving User Access Complexity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing software application access in dynamic workplace environments is challenging due to the ever-changing user base and proliferation of software applications, leading to difficulties in ensuring intended access while managing cost and security risks.

Innovation Solution

An identity mapping system that gathers user data from multiple repositories to create a unique user identity database, assigning a single ID to each user and prioritizing data sources for reliability, enabling efficient management of software access by recommending application additions or deletions based on user roles and responsibilities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple user names are associated with each user for different software applications, then user access flexibility is improved, but system complexity and security risk increase

Engineering Contradiction:
Improveuser access flexibilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments user identity management by creating separate user profiles for each software application while maintaining a central directory service. Each user can have different usernames and access rights for different applications (e.g., HR system, email, file server), allowing flexible access control without managing a single complex identity system. The directory service breaks down the complexity into manageable segments that can be independently configured.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A central directory service acts as an intermediary between users and multiple software applications. This mediator manages user credentials, authentication, and authorization across all applications centrally, reducing the complexity that would otherwise exist in each individual application's access control system. The directory service handles the complexity of multiple usernames and permissions, presenting a simplified interface to both users and applications.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If user access to software applications is tightly controlled, then security risk is reduced, but user productivity and access efficiency worsen

Engineering Contradiction:
ImprovesecurityVSAvoiduser productivity
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary actions by pre-configuring user profiles with appropriate access rights in the directory service before users need to access software applications. User credentials and permissions are established in advance based on their roles and responsibilities, allowing them to access required applications immediately without manual approval processes or security checks at access time, thus maintaining security while enabling productivity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The directory service provides feedback mechanisms to monitor and manage user access across applications. Administrators can review user permissions, modify access rights based on changing user roles, and audit access patterns to ensure security compliance. This feedback loop allows the system to maintain tight security controls while adapting to user needs, ensuring that productivity is not compromised by overly restrictive access policies.

Inventive Principle:
Principle #23Feedback

3Measurement precision

If comprehensive user data is collected from multiple repositories, then user identification accuracy is improved, but data management complexity and processing time increase

Engineering Contradiction:
Improveuser identification accuracyVSAvoiddata processing time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-collecting and storing user data from multiple repositories (HR systems, application databases, authentication systems) in the central directory service before identification is needed. User profiles are populated with relevant attributes and credentials in advance, so when user identification is required, the system can quickly retrieve accurate information without performing complex data gathering and verification operations at the moment of access.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9330134B2User identity mapping system and method of use
Publication Date: 2016.05.03 FAIRWARNING IP LLC
  • US9330134B2 patent drawing
  • US9330134B2 patent drawing
  • US9330134B2 patent drawing

AI summary

An identity mapping system includes an identity mapping database and a master user table (MUT) communicatively coupled with the identity mapping database. The MUT includes a record having at least one record data field, a unique user identification (ID) field and at least one user data field. The at least one user data field contains data from a software application.