Cross-Domain Authorization Policy Management for Secure API Calls

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The security of cross-domain call services is compromised due to irrational and untimely cross-domain authorization policies in front-end and back-end separated technical architectures, leading to potential vulnerabilities in cross-domain resource sharing.

Innovation Solution

A method and platform for processing cross-domain authorization and control that involve displaying authorization options, generating policies based on user input, associating these policies with API objects, and establishing routes based on predefined permissions to ensure secure and timely cross-domain calls.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If cross-domain authorization policies are formulated for shared resources in front-end and back-end separated architectures, then cross-domain call services can be enabled between different terminals or application servers, but the security of these services is compromised due to irrational and untimely policy formulation

Engineering Contradiction:
Improvecross-domain call service capabilityVSAvoidsecurity of cross-domain call service
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary actions by pre-defining authorization policies and associating them with API objects before cross-domain calls occur. The policy management platform allows administrators to configure authorization rules in advance, which are then automatically applied when cross-domain requests are made, ensuring security is established before potential threats arise.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

A policy management platform is introduced as an intermediary between the front-end and back-end systems. This platform receives policy deployment requests, generates authorization policies, and associates them with API objects, thereby mediating the authorization process and ensuring that security policies are properly formulated and applied without requiring direct modification of the core call services.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of manufacture

If traditional policy management methods are used in cross-domain architectures, then implementation is straightforward, but configuration and update costs are high and policies are not timely

Engineering Contradiction:
Improveease of policy implementationVSAvoidconfiguration and update time
Core Design Contradiction:
Ease of manufactureVSLoss of time

Solution Approach 1:

The policy management platform enables self-service by automatically generating authorization policies based on predefined templates and rules. When a policy deployment request is received, the system automatically creates the policy, associates it with the relevant API object, and deploys it without requiring manual configuration for each individual policy, thereby reducing configuration time and effort.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system utilizes parameter changes by allowing flexible configuration of policy parameters such as authorization scopes, time limits, and resource identifiers. These parameters can be modified through the policy deployment request, enabling the system to adapt policies to different scenarios without changing the overall policy structure, thus reducing update complexity and time.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS20250315514A1Method of processing cross-domain authorization and method of processing cross-domain call
Publication Date: 2025.10.09 BOE TECHNOLOGY GROUP CO LTD
  • US20250315514A1 patent drawing
  • US20250315514A1 patent drawing
  • US20250315514A1 patent drawing

AI summary

A method of processing a cross-domain authorization includes: displaying, in response to a received policy deployment request, at least one cross-domain authorization option associated with a target application, wherein the target application is an application to be configured for a cross-domain authorization indicated by the policy deployment request; acquiring policy description data input by a user for the at least one cross-domain authorization option; generating a cross-domain authorization policy for the target application according to the policy description data; and associating the cross-domain authorization policy with an API object of the target application, so as to perform a cross-domain call for the target application according to the associated API object and cross-domain authorization policy. A method of processing a cross-domain call, a platform of processing a cross-domain control, a system of implementing a cross-domain call, an electronic device, a computer-readable storage medium, and a computer program product are also disclosed.