Third-Party Authorization Verification with Event-Driven Entitlements
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Transactional systems with multiple core systems face complexity in seamless interfacing and challenges in determining user authentication and entitlements due to separate repositories maintained by each core system.
Innovation Solution
An authorization platform with a policy engine maintains an entitlement repository and event listeners to update entitlement data based on core system events, allowing verification without polling, thus reducing computational overhead and improving performance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple core systems maintain separate repositories of user accounts and entitlements, then each core system can independently manage its own data, but the system becomes complicated and seamless interfacing becomes difficult
Solution Approach 1:
The patent introduces an authorization platform as an intermediary component that sits between multiple core systems and third-party systems. This platform maintains a unified entitlement repository and handles authentication/authorization decisions centrally, allowing core systems to maintain their own separate repositories while avoiding direct complexity in interfacing with each other. The authorization platform mediates communications and resolves entitlements across all core systems.
2Reliability
If the authorization platform polls core systems for entitlement data, then it can obtain current entitlement information, but computing resources are consumed and performance is reduced
Solution Approach 1:
The patent implements an event-driven architecture where core systems publish entitlement-modifying events (such as account creation, user addition, or permission changes) to the authorization platform. The platform subscribes to these events and automatically updates its entitlement repository when changes occur. This eliminates the need for polling while ensuring the authorization platform always has current entitlement data, thus maintaining both reliability and performance.
3Productivity
If the authorization platform maintains entitlement data separately from core systems, then it can verify third-party authorization efficiently, but the system architecture becomes more complex
Solution Approach 1:
The patent segments the system into distinct functional components: core systems that manage their own data, an authorization platform that handles authentication/authorization decisions, and third-party systems that make requests. The authorization platform maintains its own entitlement repository that is updated by events from core systems. This segmentation allows efficient third-party verification through a single unified data source without requiring the authorization platform to be deeply integrated with each core system's internal structure.
Data Source
AI summary
A computing system includes a core system having an event engine and one or more interfaces; an authorization platform having authorization clients configured to maintain entitlement data, one or more event listeners, and one or more administration layer servers capable of configuring the one or more authorization clients; and a request router configured to route incoming electronic access requests to the authorization platform. The authorization platform can compute, by the event listener, that an entitlement event has occurred at the core system, communicate event data descriptive of the event to the one or more administration layer servers, communicate the event data to the one or more authorization clients, generate updated entitlement data based on the event data; and update the entitlement data based on the updated entitlement data.