Anonymized interface for ticket based authentication

A system comprising:

• at least one processor;
• and
• memory storing:
• an identifier map, the identifier map storing at least one entry that maps a session identifier to at least one mock identifier-protected identifier pair;
• associations between tickets and subject entities;
• and
• instructions that, when executed by the at least one processor, cause the system for perform operations including:
• receiving a request for information that includes a ticket,
• determining that the ticket matches an entry in the associations between tickets and subject entities,
• responsive to determining that the ticket matches the entry:
• generating a session identifier;
• obtaining information from a database for a subject entity associated with the ticket in the associations;
• for each of at least one protected identifier in the information:
• generating a mock identifier for a mock identifier-protected identifier pair,
• replacing the protected identifier with the mock identifier in the information, and
• adding an entry to the identifier map that includes the generated session identifier and the mock identifier-protected identifier pair;
• removing protected information from the information;
• and
• providing a user interface configured to provide access to the information and to provide the generated session identifier to a computing device that provided the request for information;
• receiving a second request for information that includes a first session identifier and a first mock identifier,
• identifying an entry in the identifier map for the first session identifier, and
• responsive to identifying the entry for the first session identifier:
• using a protected identifier from the mock identifier-protected identifier pairs of the entry to obtain second information that is responsive to the second request,
• replacing, in the second information, at least one protected identifier with a corresponding mock identifier of the at least one protected identifier from the mock identifier-protected identifier pairs,
• removing protected information from the second information, and
• providing a user interface configured to provide access to the second information.

A non-transitory computer-readable medium storing instructions that, when executed by at least one processor, cause a computing system to:

• send a communication to a communication address for a subject entity, the communication including a ticket generated for the subject entity;
• receive a request for information that includes the ticket;
• determine whether the ticket is valid;
• responsive to determining that the ticket is valid:
• obtain information for the subject entity,
• generate a session identifier,
• for each of at least one protected identifier in the information:
• generate a respective mock identifier;
• add a map record that includes the session identifier, the protected identifier, and the respective mock identifier;
• and
• replace the protected identifier with the respective mock identifier in the information, and
• provide a user interface configured to provide the information to a device associated with the session identifier;
• receive a second request for information that includes a session identifier and a first mock identifier;
• locate the map record for the session identifier and the first mock identifier;
• and
• responsive to locating the map record:
• use a protected identifier in the map record to obtain second information that is responsive to the second request,
• remove protected information from the second information, and
• provide the second information for display in a user interface associated with the communication address.