Centralized Authorization Reference Object for Multi-Vendor Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current approaches require users to submit multiple authorization requests to different vendor authorization servers for access to data resources, leading to inefficiencies and increased queries to these servers.

Innovation Solution

A central management server system is introduced that generates and stores authorization reference objects, which are used to service subsequent requests for access to data resources, reducing the need for direct queries to vendor-specific authorization servers through an intermediate security token service (STS).

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If users submit separate authorization requests to each vendor's authorization server, then each vendor can verify access independently, but the system complexity and number of requests increase significantly

Engineering Contradiction:
Improveauthorization verificationVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent combines multiple vendor authorization servers into a single centralized authorization server that manages all vendor authorizations. Instead of users interacting with multiple separate authorization servers, the system merges them into one unified server that handles all authorization requests, thereby reducing system complexity while maintaining reliable verification through centralized control

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The centralized authorization server performs multiple functions: it acts as an authorization server for multiple vendors, maintains authorization information for different vendors, generates access tokens for various vendors, and manages user credentials universally. This multi-functional approach eliminates the need for separate authorization servers for each vendor, reducing overall system complexity

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

2Reliability

If users submit separate authorization requests to each vendor, then each vendor's authorization server can be queried independently, but the number of requests and time consumption increase

Engineering Contradiction:
Improveauthorization accessVSAvoidtime consumption
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary action by pre-storing authorization information for multiple vendors in a centralized authorization server during an initial setup phase. When a user needs access to multiple vendors, the authorization information is already prepared and stored, eliminating the need for repeated real-time queries to multiple vendor authorization servers, thus reducing time consumption while maintaining reliable access

Inventive Principle:
Principle #10Preliminary action

3Reliability

If multiple vendor authorization servers are queried separately, then each vendor's security policies can be enforced independently, but the load on authorization servers increases

Engineering Contradiction:
Improvesecurity policy enforcementVSAvoidserver load
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent merges multiple vendor authorization servers into a single centralized authorization server that handles all authorization requests. This consolidation reduces the overall server load by eliminating redundant infrastructure and consolidating processing power into one server, while still enforcing security policies through centralized management and configuration

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS12126621B2Multiple vendor authorization
Publication Date: 2024.10.22 SAP SE
  • US12126621B2 patent drawing
  • US12126621B2 patent drawing
  • US12126621B2 patent drawing

AI summary

Systems and processes for managing authorizations for multiple vendors at an enterprise service are provided. Responsive to a request to onboard an authorization for access to data resources of a targeted vendor, a central management server may receive, from an authorization server for the targeted vendor, authorization information. The authorization information may be received indirectly, via a security token service. An authorization reference object may be generated to store the authorization information, and the authorization reference object may be stored in a database. Subsequent requests for access to the data resources of the targeted vendor may be serviced using the authorization reference object stored in the database.