Methods and systems for external system authentication and file access control
AssigneeInkit, Inc.
InventorMichael McCarthy
Life of this patent
Estimating the term…
Abstract
The present disclosure generally relates to methods, systems, apparatuses, and non-transitory computer readable media for managing file generation and retention. These systems may be of used across a wide range of businesses to significantly automate the generation and storage of files. By utilizing nested file templates as described below, systems of the present disclosure may increase the ease in which a file template may be generated. Moreover, by using the file retention storage system described below, system of the present disclosure may simplify the process of ensuring files are retained for an appropriate amount of time and further assuring that files are deleted when they no longer need to be retained.
Claims20
A method for managing access to generated files displayed on a third-party application, comprising:
- storing a first file created from a file template in non-volatile memory accessible by a first server;
- receiving, at the first server, a request to connect with respect to a first user account of the first server, wherein:
- the request to connect is received from a second server;
- the first user account is associated with a first user;
- and
- the second server is associated with a third-party portal;
- authenticating, in response to receiving the request to connect, the second server for connecting to the first user account based on the received request to connect with the first user account, wherein the authentication of the request to connect is performed by the first server;
- generating, at the first server, a first uniform resource identifier (URI) associated with the first file, wherein the first URI links to a first resource comprising the first file;
- transmitting, in response to authenticating the request to connect, the first URI and information identifying the first file to the second server, wherein the first URI and information identifying the first file are transmitted from the first server;
- detecting, by the first server, a deletion-triggering event;
- and
- deleting the first file from the non-volatile memory in response to detecting the deletion-triggering event.
A file management system, comprising:
- a first server, wherein the first server is configured to:
- store a first file created from a template in non-volatile memory accessible by the first server;
- receive a request to connect with respect to a first user account of the first server, wherein:
- the request to connect is received from a second server;
- the first user account is associated with a first user;
- and
- the second server is associated with a third-party portal;
- authenticate, in response to receiving the request to connect, the second server for connecting to the first user account based on the received request to connect with the first user account;
- generate a first uniform resource identifier (URI) associated with the first file, wherein the first URI links to a first resource comprising the first file;
- transmit, in response to authenticating the request to connect, the first URI and information identifying the first file to the second server;
- detect a deletion-triggering event;
- and
- delete the first file from the non-volatile memory in response to detecting the deletion-triggering event.
A non-transitory computer readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to manage access to generated files displayed on a third-party application by:
- storing a first file created from a file template in non-volatile memory accessible by a first server;
- receiving, at the first server, a request to connect with respect to a first user account of the first server, wherein:
- the request to connect is received from a second server;
- the first user account is associated with a first user;
- and
- the second server is associated with a third-party portal;
- authenticating, in response to receiving the request to connect, the second server for connecting to the first user account based on the received request to connect with the first user account, wherein the authentication of the request to connect is performed by the first server;
- generating, at the first server, a first uniform resource identifier (URI) associated with the first file, wherein the first URI links to a first resource comprising the first file;
- transmitting, in response to authenticating the request to connect, the first URI and information identifying the first file to the second server, wherein the first URI and information identifying the first file are transmitted from the first server;
- detecting, by the first server, a deletion-triggering event;
- and
- deleting the first file from the non-volatile memory in response to detecting the deletion-triggering event.
Dependencies are inferred from the claim text.