Blockchain Token Authentication for Cross-Tenant Meeting Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network-based communication systems face challenges in securely authenticating participants from untrusted domains, leading to inefficient configuration of communication sessions and resource waste due to the need for manual setup and waiting rooms.
Innovation Solution
Utilizing blockchain tokens, specifically non-fungible tokens (NFTs), to authenticate participants by recording them on a blockchain, ensuring secure and automated application of user-specific settings without the need for manual configuration or waiting rooms.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional authentication methods are used for users from outside trusted tenants, then the configuration process becomes complex and time-consuming, but security cannot be ensured
Solution Approach 1:
The system performs preliminary authentication by verifying the user's blockchain account balance before allowing communication session configuration. This preliminary check ensures that only users with sufficient cryptocurrency can proceed, eliminating the need for complex post-authentication configuration steps and ensuring security from the outset.
Solution Approach 2:
The patent introduces a blockchain-based intermediary authentication mechanism that mediates between traditional authentication systems and communication session management. This intermediary layer uses cryptocurrency verification as a universal credential that works across tenant boundaries, simplifying the authentication process while maintaining security.
2Reliability
If manual configuration processes are used for external participants, then security policies can be enforced, but the process is inefficient and resource-intensive
Solution Approach 1:
The system enables self-service authentication where external participants automatically prove their identity and credentials by presenting their blockchain account information. The system autonomously verifies their cryptocurrency balance and grants appropriate access rights without requiring manual security policy configuration, dramatically improving efficiency while maintaining security.
Solution Approach 2:
The patent changes the authentication parameter from traditional username/password or certificate-based systems to cryptocurrency balance verification. This parameter change fundamentally alters the authentication mechanism, making it both more secure (cryptographically verified) and more efficient (automated verification process).
3Adaptability or versatility
If traditional authentication systems are used, then existing user databases can be leveraged, but they cannot verify identity of participants from outside trusted tenants
Solution Approach 1:
The patent implements a universal authentication mechanism using blockchain technology that works across all tenant boundaries. The same cryptocurrency-based authentication method can verify identities of users from any tenant or external participant, making the system highly adaptable without requiring separate authentication systems for different user types.
Solution Approach 2:
The system replaces complex mechanical authentication systems (multiple databases, trust relationships, manual verification processes) with a cryptographic blockchain-based system. This substitution simplifies the overall architecture by using the inherent security properties of blockchain technology rather than trying to build security into traditional authentication frameworks.
Data Source
AI summary
Disclosed in some examples are methods, systems, devices, and machine-readable mediums which utilize authentication tokens recorded to a blockchain to identify and/or authenticate participants of a network-based communication session such as a network-based meeting. When joining the meeting, the participant may provide a token recorded on a blockchain to the communication service from the blockchain. The communication service may then identify and/or authenticate the user based upon the provided token. Various user-specific customizations and settings may then be applied and the user may be admitted to the meeting without having to enter a waiting room and be explicitly let in.