Centralized OAuth Configuration Aggregation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems require significant maintenance efforts for OAuth client configurations across multiple applications, leading to increased costs and complexity due to the need for static lists of scopes and individual client configurations.

Innovation Solution

A centrally managed application configuration system that dynamically determines and manages resources, allowing applications to declare required resources and scopes once, reducing the need for repetitive configuration and maintenance by aggregating a maximum list of resources and scopes for OAuth token acquisition.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If each application delivers its own OAuth client configurations with static lists of scopes, then each application can access required resources independently, but huge maintenance efforts are required by system administrators

Engineering Contradiction:
ImproveIndependent resource accessVSAvoidConfiguration maintenance complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges OAuth client configurations from multiple applications into a single centralized configuration. Instead of each application having separate static scope lists, the system combines all application requirements into one unified configuration that is maintained centrally, eliminating redundant maintenance efforts while preserving each application's access rights

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The centralized OAuth client configuration serves multiple applications simultaneously with a single configuration file. This universal configuration can be reused across different applications, allowing the system to manage authentication and authorization for multiple applications through one shared resource rather than requiring separate configurations for each

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

2Reliability

If static lists of scopes are provided for each client, then authorization can be granted securely, but the number of interactions for token acquisition increases

Engineering Contradiction:
ImproveSecure authorizationVSAvoidToken acquisition time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary aggregation of all scope requirements from multiple applications into a single comprehensive scope list before token acquisition. By pre-combining the scopes that need to be requested, the system reduces the number of back-and-forth interactions required during token acquisition, as all necessary permissions are requested in one unified OAuth flow rather than multiple separate flows

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If individual client configurations are maintained for multiple applications, then each application can be deployed independently, but the total cost of ownership increases

Engineering Contradiction:
ImproveIndependent application deploymentVSAvoidTotal cost of ownership
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent combines multiple individual client configurations into a single shared OAuth client configuration that serves all applications. This merging reduces the total quantity of configuration data that needs to be created, stored, and maintained, thereby lowering the total cost of ownership while still allowing each application to be deployed and accessed independently

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS9817645B2Reusable application configuration with dynamic resource determination
Publication Date: 2017.11.14 SAP SE
  • US9817645B2 patent drawing
  • US9817645B2 patent drawing
  • US9817645B2 patent drawing

AI summary

The present disclosure describes methods, systems, and computer program products for providing a deployment of applications across a distributed network environment. A computer-implemented method comprises: receiving, at a server and from a client device, a first request including an identifier of a configuration file accessible to the server and one or more identifiers for one or more resources operated by a remote resource server, wherein the resources are requested by an application executed on the client device; in response to the request, retrieving, by the server, one or more tokens associated with the requested resources; transmitting, by the server, a second request to the remote resource server, the second request including the tokens and identifying one or more data processing tasks to be performed by the resources for the application; and receiving, by the server and from the remote resource server, result data that was outputted by the resources executing the data processing tasks.