Federated Service Permission Scaling with Cached Authorization Tokens
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing federated systems face inefficiencies and high latency due to the need for multiple services to individually verify user permissions, leading to excessive network traffic and communication overhead.
Innovation Solution
An authorization token is generated by an authorization server and propagated across services, caching it for reuse, reducing the need for individual permissions checks and minimizing network calls.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If multiple services individually verify user permissions, then permission verification accuracy is improved, but network traffic and communication overhead increase
Solution Approach 1:
The patent combines permission verification across multiple services by issuing a single authorization token from the authorization server that is recognized and validated by all participating services. This eliminates the need for each service to individually verify permissions through separate network calls, thereby reducing network traffic while maintaining verification accuracy through the unified token-based approach.
Solution Approach 2:
The authorization server performs permission verification in advance by issuing an authorization token that encapsulates the user's permissions. This preliminary action allows multiple services to reuse the pre-verified permissions information without performing redundant verification steps, thereby reducing network traffic and communication overhead while maintaining verification reliability.
2Reliability
If multiple services individually verify user permissions, then permission verification accuracy is improved, but system latency increases
Solution Approach 1:
The authorization server performs permission verification in advance by issuing an authorization token that encapsulates the user's permissions. This preliminary action allows multiple services to reuse the pre-verified permissions information without performing redundant verification steps, thereby reducing system latency while maintaining verification reliability.
Solution Approach 2:
The authorization token serves as a copy of the user's permission information that can be reused across multiple services. Instead of repeatedly accessing the original permission data source, services validate the copied token information, which significantly reduces verification time and system latency while maintaining accuracy through cryptographic validation of the token.
3Productivity
If authorization tokens are cached for reuse, then system productivity is improved, but device complexity increases
Solution Approach 1:
The patent extracts the permission verification logic from individual services and centralizes it in the authorization server, which manages the authorization token cache. This extraction allows services to simply validate tokens without implementing complex caching mechanisms themselves, thereby improving system productivity while concentrating the complexity in a single specialized component rather than distributing it across all services.
Data Source
AI summary
Methods, apparatuses, or computer program products according to the present disclosure provide for service permissions scaling. In example embodiments, an apparatus receives a service request from an edge server. The apparatus may generate an authorization token based at least in part on a permissions data vector, where the authorization token is configured for access by one or more computing devices to determine whether to grant access by a first computing device associated with the requesting entity identifier to one or more resources associated with the one or more computing devices. The apparatus may then transmit the authorization token to the edge server. According to some embodiments, the authorization token may be configured for storing in an authorization token cache. In some embodiments, the authorization token may be retrieved from the authorization token cache.