General Integrations Account for Secure System Data Exchange

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Integrating systems over untrusted networks poses challenges in balancing security and convenience, as existing solutions often compromise either security or simplicity in setup and management.

Innovation Solution

The system configures a receiving system and a sending system to communicate via defined APIs, using a general integrations user account for secure and convenient data exchange, with separate access checks to ensure security and manage integrations efficiently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If separate user accounts are created for each integration between systems, then security is improved through granular access control, but device complexity and ease of operation deteriorate due to multiple credentials to manage

Engineering Contradiction:

ImprovesecurityVSAvoidintegration management complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges multiple integration-specific user accounts into a single general integrations user account that can be shared across multiple sending systems. This consolidation reduces the number of credentials to manage while maintaining security through integration records that track which systems have access to which APIs.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The general integrations user account serves multiple functions: it provides authentication for multiple sending systems, enables integration management across different system pairs, and maintains security credentials that can be reused across integrations. This multi-functional account resolves the contradiction by reducing complexity while preserving security.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Reliability

If separate user accounts are created for each integration between systems, then security is improved through granular access control, but ease of operation deteriorates due to cumbersome setup processes

Engineering Contradiction:

ImprovesecurityVSAvoidintegration setup simplicity

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The system performs preliminary action by creating a general integrations user account in advance that can be reused across multiple integrations. This eliminates the need to create new credentials for each integration, simplifying the setup process while maintaining security through the integration record system.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent enables copying of the general integrations user account credentials across multiple sending systems. Instead of creating unique accounts for each system, the same credentials can be copied and used universally, with security managed through integration records that specify which systems have access to which APIs.

Inventive Principle:

Principle #26Copying

3Ease of operation

If a general integrations user account is used for multiple systems, then ease of operation is improved through simplified setup, but security deteriorates due to broader access credentials

Engineering Contradiction:

Improveintegration setup simplicityVSAvoidsecurity

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The patent segments security management into two layers: a general integrations user account for authentication and an integration record system for authorization. The integration records specify which sending systems can access which receiving system APIs, providing granular security control despite using shared credentials. This segmentation resolves the contradiction by maintaining simplicity while preserving security.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The integration record acts as an intermediary between the general integrations user account and the API access control. It mediates security by specifying which systems have access to which APIs, allowing the system to use simple shared credentials while maintaining granular security through the intermediary integration records.

Inventive Principle:

Principle #24Intermediary (Mediator)

4Reliability

If multiple credentials are required for different integrations, then security is improved through access control, but productivity deteriorates due to time-consuming credential management

Engineering Contradiction:

ImprovesecurityVSAvoidintegration setup efficiency

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The patent merges multiple integration credentials into a single general integrations user account, eliminating the need to create and manage separate credentials for each integration. This consolidation significantly improves productivity by reducing credential management overhead while maintaining security through the integration record system.

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS11240229B2Systems and methods for integrating systems over untrusted networks

Publication Date: 2022.02.01 ATLASSIAN PTY LTD

AI summary

Described herein is a computer implemented method for configuring a receiving system to receive data from a sending system. The method comprises receiving an integration creation request from a client application. In response, a specific integration user account is created with credentials which provide access to the receiving system. The credentials are communicated to the client application. In addition, an integration record comprising details in respect of the integration is created, stored, and associated with the specific integration user account.