Application Authentication Token Embedding in Filenames
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional methods for authenticating applications on computing devices are tedious and cumbersome, especially when dealing with sensitive data, as they often require users to manually enter long and complicated passwords, and inserting authentication tokens into encrypted application packages is impractical for large-scale distribution.
Innovation Solution
A method where an authentication token is embedded within the filename of an application package, allowing the endpoint device to authenticate with the application without requiring manual user input, by using a host server to generate and embed the token, and an authentication agent to identify and utilize it for secure access.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If users manually provide authentication credentials when installing applications, then authentication security is improved, but user convenience and installation speed deteriorate
Solution Approach 1:
The authentication token is embedded in the application package before distribution, so that when users install the application, authentication is already prepared and automatic. This eliminates the need for manual credential entry during installation while maintaining security through pre-generated tokens.
Solution Approach 2:
The system performs authentication automatically without requiring user intervention. The authentication agent within the application extracts the token and completes the authentication process autonomously, making the system self-serving rather than requiring manual user input.
2Reliability
If authentication tokens are inserted into encrypted application packages, then authentication capability is improved, but application distribution and installation complexity worsen
Solution Approach 1:
The authentication token is separated from the encrypted application package and placed in the filename instead. This segmentation allows the application to remain encrypted and unchanged while the token is carried in a separate, easily identifiable location (the filename), avoiding the complexity of modifying encrypted packages.
3Reliability
If long and complicated passwords are required for authentication, then data security is improved, but authentication time and user effort increase
Solution Approach 1:
The system uses short-lived authentication tokens instead of long-lasting passwords. These tokens are generated for each application installation, are sufficient for the authentication purpose, and then discarded. This eliminates the need for users to remember or re-enter long complicated passwords while maintaining adequate security through time-limited tokens.
Data Source
AI summary
The disclosed computer-implemented method for authenticating applications installed on computing devices may include (i) requesting to download, onto an endpoint device, an application from a host server, (ii) receiving the application from the host server after the host server has (a) generated an authentication token to be used to authenticate the application on the endpoint device and (b) embedded the authentication token within a filename of the application, (iii) installing the application onto the endpoint device, (iv) identifying the authentication token within the filename of the application, and (v) using the authentication token to authenticate the endpoint device to the application such that a user of the endpoint device is provided access to the application. Various other methods, systems, and computer-readable media are also disclosed.