Transaction Credential Segmentation for Long-Lived Authorization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems fail to authorize long-lived transactions when the credentials used for authorization have expired, leading to potential execution issues due to expired credentials during delayed or long-running transactions.
Innovation Solution
A method and system that create a transaction credential for long-lived transactions, allowing their execution even after login credentials have expired, by determining authorization based on the transaction credential, which can be valid for a specified time period or date, ensuring continued access to data resources without requiring active login.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional credential-based authorization is used for transactions, then security is maintained through expired credential validation, but long-lived transactions cannot execute after credential expiration
Solution Approach 1:
The authorization system is segmented into two distinct credential types: login credentials for initial authentication and transaction credentials for execution authorization. This segmentation allows login credentials to expire while transaction credentials remain valid, resolving the contradiction between security and long-lived transaction execution.
Solution Approach 2:
Transaction credentials are created in advance during the login phase, before the actual transaction execution. This preliminary action ensures that authorization is pre-established and can be validated later even after login credentials expire, enabling long-lived transactions to complete successfully.
2Ease of operation
If login credentials are required for every transaction execution, then security is maintained, but transactions fail when credentials expire
Solution Approach 1:
Transaction credentials act as an intermediary between login credentials and transaction execution. They bridge the gap by carrying authorization information independently of login credential validity, allowing transactions to execute continuously even after login credentials expire.
3Duration of action of moving object
If credentials are extended to support long-lived transactions, then transaction continuity is improved, but security risk increases from potential credential misuse
Solution Approach 1:
Different credential types have different validity characteristics tailored to their specific purposes. Login credentials have short validity for security, while transaction credentials have extended validity for execution continuity. This localized quality assignment optimizes both security and transaction reliability without compromising either.
Data Source
AI summary
A method of authorizing a transaction may include receiving, by a hosted service from a client device, a request to access an account and determining whether a user of the client device is permitted to access the account. The method may include, in response to determining that the user is permitted to access the account, receiving, from the client device, a request to initiate a transaction, determining whether the transaction is a long-lived transaction, in response to determining that the transaction is a long-lived transaction, creating a transaction credential associated with the long-lived transaction, and determining, based at least in part on the transaction credential, whether the execution of the long-lived transaction is authorized.