Token-Based Access Control via Role Assumption
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In large-scale computing environments, propagating credentials for access control is difficult, costly, and introduces vulnerabilities, while short-term credentials lack the group behavior support of user-based systems.
Innovation Solution
Implementing a two-step role assumption process using short-term security tokens, where a principal assumes an intermediary role and then a destination role, with a token service verifying the intermediary role before granting access, and using a credential renewal service for token updates and revocation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If user-based credential systems are used to support group behavior, then group access rights are enabled, but credential propagation becomes difficult and costly in large-scale environments
Solution Approach 1:
The patent introduces role-assumption as an intermediary mechanism between users and resources. Instead of directly propagating user credentials to multiple resources, users assume roles that represent groups or resource access patterns. This role-assumption layer mediates the authentication process, allowing users to gain access to resources associated with assumed roles without requiring direct credential propagation to each resource.
Solution Approach 2:
The patent creates role-identities as copies or representations of user identities with specific access permissions. When a user assumes a role, they temporarily adopt the permissions associated with that role without sharing their actual credentials. This copying approach allows multiple users to assume the same role and access the same resources without requiring credential propagation among users or from administrators to each user.
2Reliability
If short-term credentials are distributed for authentication, then security is improved, but group behavior support is lost compared to user-based systems
Solution Approach 1:
The patent implements dynamic role-assumption where users can temporarily assume roles for specific durations or until the role is exited. This dynamic approach combines the security benefits of short-term credentials with the flexibility of group behavior. Users obtain short-term role-identities that expire or can be revoked, yet multiple users can simultaneously assume the same role to achieve group-like access patterns.
Solution Approach 2:
The role-assumption mechanism serves multiple functions: it provides short-term security credentials, enables group behavior through shared role access, and maintains centralized control. A single role-identity can be assumed by multiple users, effectively creating group access rights without requiring credential propagation or long-term credential sharing.
3Ease of operation
If traditional credential propagation is implemented, then access control is established, but vulnerabilities increase in the system
Solution Approach 1:
The patent extracts the actual user credentials from the authentication process and replaces them with role-identities. User credentials remain securely stored in the identity provider and are never propagated to resources. Instead, short-term role-identities are issued that reference the user's assumed roles, effectively taking out the vulnerable credential propagation step while maintaining access control functionality.
Solution Approach 2:
The patent uses short-term, disposable role-identities instead of long-term reusable credentials. These role-identities have limited lifetimes and can be revoked or expire automatically, reducing the window of opportunity for attackers. If compromised, the damage is limited because the credentials are short-lived and can be quickly rotated without affecting the underlying user credentials.
Data Source
AI summary
One or more clients of a service may obtain access to resources of the service using one or more roles. A role may be used to delegate access to resources that a client normally would not otherwise have access to. A requestor may make a request to assume an intermediary role and receive a first token that enables assumption of the intermediary role. The requestor, after assuming the intermediary role, may request to assume to assume a destination role and receive a second token that enables the requestor to access one or more computing resources by assuming the destination role.


