Mobile Device Code-Based Authorization System
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for authenticating mobile communications devices for secure web services are cumbersome, often requiring users to manually input usernames and passwords across multiple devices, and lack efficient mechanisms for device authorization.
Innovation Solution
A method and system that generates a readable code with a secret token, allowing mobile devices to authenticate by scanning the code, which is stored on an authentication server, enabling device authorization and replacing traditional username and password inputs for secure web service access.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If traditional username and password authentication is used across multiple devices, then security is maintained, but user convenience and authentication speed deteriorate due to manual input requirements
Solution Approach 1:
The system performs preliminary authentication by having the user scan a code once to establish a trusted device relationship. This preliminary action stores authentication credentials on the mobile device, eliminating the need for repeated manual authentication on the same device while maintaining security.
Solution Approach 2:
The system creates a copy of authentication credentials (trusted device identifier) on the mobile device after initial verification. This copy allows the device to authenticate itself without requiring the user to repeatedly enter username and password, significantly improving convenience and reducing authentication time.
2Ease of operation
If device authorization mechanisms are simplified for mobile devices, then ease of operation improves, but security reliability may worsen due to reduced authentication rigor
Solution Approach 1:
The system introduces an intermediary authentication server that mediates between the user and the mobile device. The server verifies the mobile device's identity through code scanning and establishes trusted relationships, providing both simplified user interaction and maintained security through server-side verification and validation.
Solution Approach 2:
The system replaces the mechanical process of manual username and password input with an optical scanning mechanism. The mobile device scans a code to automatically transmit device identifiers for authentication, eliminating manual typing while maintaining security through server-side verification of the transmitted identifiers.
3Productivity
If manual username and password input is required on each device, then security is maintained, but productivity and access speed deteriorate
Solution Approach 1:
The system performs preliminary authentication by having the user scan a code once to establish a trusted device relationship. This preliminary action stores authentication credentials on the mobile device, eliminating the need for repeated manual authentication on the same device while maintaining security.
Solution Approach 2:
The authentication system creates a universal trusted device identifier that works across multiple web services and contexts. Once a mobile device is authenticated through code scanning, the trusted device relationship provides universal access to protected resources without requiring device-specific configuration or repeated authentication procedures.
Data Source
AI summary
A system and method for authenticating mobile communications devices. The method comprises: generating a code corresponding to a user configured to be rendered on a rendering device to produce a rendered code, the rendered code being readable by a mobile communications device having a code reading device, the rendered code comprising a secret token; storing the secret token along with information identifying the user on a first storage device; providing the code to the user; receiving, at the authentication server, a setup message from the mobile device, the message includes a device identifier and the secret token; comparing the received secret token and the secret token stored on the first storage device; if the received secret token matches the secret token stored on the first storage device, storing, on a second storage device, information identifying the user and a trusted device value corresponding to the device identifier.