Entity authentication for pre-authenticated links
US-2024396898-A1 · Nov 28, 2024 · US
US12574432B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12574432-B2 |
| Application number | US-202318484231-A |
| Country | US |
| Kind code | B2 |
| Filing date | Oct 10, 2023 |
| Priority date | Oct 7, 2022 |
| Publication date | Mar 10, 2026 |
| Grant date | Mar 10, 2026 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
The present disclosure relates to systems, non-transitory computer-readable media, and methods for generating a secure upload URL, receiving a file upload to a first draft data store, and transferring the file from the first draft data store to a first final data store. In particular, in one or more embodiments, the disclosed systems transfers the file from the first draft data store to a first final data store based on the file meeting predetermined file attributes associated with the first draft data store. Moreover, the disclosed system provides to an agent device access to the file based on access permissions corresponding to the first final data store.
Opening claim text (preview).
What is claimed is: 1 . A computer-implemented method comprising: receiving, from a client device, an upload request comprising information associated with a file; identifying a first draft data store from a plurality of draft data stores based on a content category identified within the upload request; based at least in part on the information associated with the file, generating a secure upload URL to the first draft data store; providing the secure upload URL to the client device for the client device to upload the file to the first draft data store; transferring the file from the first draft data store to a first final data store based on the file meeting predetermined file attributes associated with the first draft data store; and providing, to an agent device, access to the file based on access permissions corresponding to the first final data store. 2 . The computer-implemented method of claim 1 , wherein the content category identified within the upload request is a content category from a set of content categories comprising disputed transactions, personal identification, or account updates. 3 . The computer-implemented method of claim 2 , wherein the predetermined file attributes associated with the first draft data store are different from predetermined file attributes associated with a second draft data store. 4 . The computer-implemented method of claim 1 , further comprising: providing a second secure upload URL for the client device to upload a second file to the first draft data store; determining the second file does not meet the predetermined file attributes associated with the first draft data store by determining a file name, a file size, file content, or a file type does not satisfy the predetermined file attributes associated with the first draft data store; and preventing transfer of the second file into the first final data store. 5 . The computer-implemented method of claim 1 , wherein transferring the file from the first draft data store to the first final data store comprises: creating a duplicate file based on the file; transferring the duplicate file to the first final data store; and removing the file from the first draft data store after a predetermined period. 6 . The computer-implemented method of claim 1 , further comprising generating the secure upload URL to expire after a predetermined period. 7 . The computer-implemented method of claim 1 , wherein providing access to the file based on the access permissions corresponding to the first final data store comprises: providing to the agent device an authorization key for making API calls; receiving an API call from the agent device with an indication of the authorization key; and returning a secure access URL to the agent device to provide access to the file. 8 . A non-transitory computer-readable medium storing instructions that, when executed by at least one processor, cause a computer system to: receive, from a client device, an upload request comprising information associated with a file; identify a first draft data store from a plurality of draft data stores based on a content category identified within the upload request; based at least in part on the information associated with the file, generate a secure upload URL to the first draft data store; provide the secure upload URL to the client device for the client device to upload the file to the first draft data store; transfer the file from the first draft data store to a first final data store based on the file meeting predetermined file attributes associated with the first draft data store; and provide, to an agent device, access to the file based on access permissions corresponding to the first final data store. 9 . The non-transitory computer-readable medium of claim 8 , wherein the content category identified within the upload request is a content category from a set of content categories comprising disputed transactions, personal identification, or account updates. 10 . The non-transitory computer-readable medium of claim 9 , wherein the predetermined file attributes associated with the first draft data store are different from predetermined file attributes associated with a second draft data store. 11 . The non-transitory computer-readable medium of claim 8 , further causing the computer system to: provide a second secure upload URL for the client device to upload a second file to the first draft data store; determine the second file does not meet the predetermined file attributes associated with the first draft data store by determining a file name, a file size, file content, or a file type does not satisfy the predetermined file attributes associated with the first draft data store; and prevent transfer of the second file into the first final data store. 12 . The non-transitory computer-readable medium of claim 8 , wherein providing access to the agent device based on access permissions of the first final data store comprises providing the agent device with a permanent secure access URL and a key that indicates a storage location of the first final data store. 13 . The non-transitory computer-readable medium of claim of claim 12 , further comprising assigning agent conditions to the first final data store. 14 . The non-transitory computer-readable medium of claim 13 , further causing the computer system to: receive, from a second agent device, a request to access the file via the permanent secure access URL; identify for the second agent device, the agent conditions for the first final data store; and provide file access to the second agent device when the second agent device satisfies the agent conditions. 15 . A system comprising: at least one processor; and at least one non-transitory computer-readable storage medium storing instructions that, when executed by the at least one processor, cause the system to: receive, from a client device, an upload request comprising information associated with a file; identify a first draft data store from a plurality of draft data stores based on a content category identified within the upload request; based at least in part on the information associated with the file, generate a secure upload URL to the first draft data store; provide the secure upload URL to the client device for the client device to upload the file to the first draft data store; transfer the file from the first draft data store to a first final data store based on the file meeting predetermined file attributes associated with the first draft data store; and provide, to an agent device, access to the file based on access permissions corresponding to the first final data store. 16 . The system of claim 15 , wherein transferring the file from the first draft data store to the first final data store causes the system to: create a duplicate file based on the file; transfer the duplicate file to the first final data store; and remove the file from the first draft data store after a predetermined period. 17 . The system of claim 15 , further causing the system to generate the secure upload URL to expire after a predetermined period. 18 . The system of claim 15 wherein providing access to the file based on the access permissions corresponding to the first final data store causes the system to: provide to the agent device an authorization key for making API calls; receive an API call from the agent device with an indication of the authorization key; and return a secure access URL to the agent device to provide acce
for controlling access to devices or network resources · CPC title
Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s) (network architectures or network communication protocols for key distribution in a packet data network H04L63/062) · CPC title
Access rights, e.g. capability lists, access control lists, access tables, access matrices · CPC title
to a system of files or objects, e.g. local or distributed file system or database · CPC title
Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.