Secure content management through authentication

A system comprising:

• at least one device including a hardware processor;
• the system being configured to perform operations comprising:
• accessing registry information, wherein the registry information comprises, for each resource of a plurality of resources:
• an identifier;
• and
• a field-to-authentication-tier mapping that specifies an authentication tier associated with one or more data fields;
• wherein the field-to-authentication-tier mapping comprises registry information that associates individual data fields with respective authentication tiers;
• based at least in part on the registry information, identifying:
• a first authentication tier associated with a first data field associated with the first resource;
• and
• a second authentication tier associated with a second data field associated with the first resource;
• in response to determining that the client is associated with the first authentication tier, eager-fetching the first data field by retrieving data for the first data field;
• in response to determining that the client is not associated with the second authentication tier, lazy-fetching the second data field by providing a reference link for accessing the second data field.

One or more non-transitory computer readable media comprising instructions which, when executed by one or more hardware processors, cause performance of operations comprising:

• accessing registry information, wherein the registry information comprises, for each resource of a plurality of resources:
• an identifier;
• and
• a field-to-authentication-tier mapping that specifies an authentication tier associated with one or more data fields;
• wherein the field-to-authentication-tier mapping comprises registry information that associates individual data fields with respective authentication tiers;
• based at least in part on the registry information, identifying:
• a first authentication tier associated with a first data field associated with the first resource;
• and
• a second authentication tier associated with a second data field associated with the first resource;
• in response to determining that the client is associated with the first authentication tier, eager-fetching the first data field by retrieving data for the first data field;
• in response to determining that the client is not associated with the second authentication tier, lazy-fetching the second data field by providing a reference link for accessing the second data field.