System and method for providing access to secured content field

A computer-implemented system for providing access to secured content on a provisioning entity system, the system comprising:

• a communication interface;
• at least one processor;
• memory in communication with said at least one processor;
• and
• instructions stored in said memory, which when executed at said at least one processor causes said system to:
• receive, from a requesting entity system, a plurality of user requests to access the secured content stored at the provisioning entity system, each of the plurality of user requests received from a user of the requesting entity system and comprising a respective user ID and respective user identifying data, the user ID identifying the user with the requesting entity system without identifying the user with the provisioning entity system;
• determine, for each of the plurality of user requests, the respective user ID;
• delete the respective user identifying data from each of the plurality of user requests;
• generate, for each of the plurality of user requests having the user identifying data deleted therefrom, a respective trusted token based on the respective user request, the trusted token comprising at least a variable term different for each of the trusted tokens generated for the plurality of user requests;
• add a proof of authentication to each of the trusted tokens to enable the provisioning entity system to validate the respective trusted token;
• and
• transmit at least one of the trusted tokens to the requesting entity system for use by the requesting entity in a subsequent request to the provisioning entity system to access the secured content.

A non-transitory computer-readable storage medium storing instructions which when executed cause at least one computing device to:

• receive, from a requesting entity system, a plurality of user requests to access secured content stored at a provisioning entity system, each of the plurality of user requests received from a user of the requesting entity system and comprising a respective user ID and respective user identifying data, the user ID identifying the user with the requesting entity system without identifying the user with the provisioning entity system;
• determine, for each of the plurality of user requests, the respective user ID;
• delete the respective user identifying data from each of the plurality of user requests;
• generate, for each of the plurality of user requests having the user identifying data deleted therefrom, a respective trusted token based on the respective user request, the trusted token comprising at least a variable term different for each of the trusted tokens generated for the plurality of user requests;
• add a proof of authentication to each of the trusted tokens to enable the provisioning entity system to validate the respective trusted token;
• and
• transmit at least one of the trusted tokens to the requesting entity system for use by the requesting entity in a subsequent request to the provisioning entity system to access the secured content.