Secure content management through authentication
Techniques are described herein for performing authentication, and also “eager” or “lazy” fetch of data, for restricted webpages based on the restricted webpages being associated with an authentication tier in an AASD registry. Inclusion of a restricted webpage in the AASD registry enables AASD-based authentication for the webpage. According to embodiments, information for a restricted webpage included in the AASD registry includes one or more of the following for the webpage: an identifier, an authentication level, allowed fields, eager fetch fields, one or more sources for one or more fields, etc. When information for a webpage is included in the AASD registry, that information is used to perform eager fetch for one or more fields of the webpage that are not associated with authentication requirements indicated in the AASD registry information, or whose authentication requirements are already fulfilled by the requesting client.
1 . A computer-executed method, comprising:
receiving a request associated with a client to access a first resource;
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;
wherein the method is performed by one or more computing devices comprising a hardware processor.
2 . The computer-executed method of claim 1 , wherein eager-fetching the first data field comprises retrieving the data associated with the first data field.
3 . The computer-executed method of claim 1 , wherein lazy-fetching the second data field comprises retrieving a reference link associated with the second data field.
4 . The computer-executed method of claim 1 , further comprising:
in response to determining that the client is not associated with the second authentication tier, causing an authentication request associated with the second authentication tier to be issued to the client.
5 . The computer-executed method of claim 4 , further comprising:
in response to determining that the client has satisfied the authentication requirements associated with the second authentication tier, retrieving the data associated with the second data field.
6 . The computer-executed method of claim 1 , wherein the registry information references a plurality of authentication tiers, wherein each authentication tier is associated with a set of authentication requirements.
7 . The computer-executed method of claim 1 , wherein the identifier associated with each resource is a URL.
8 . 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.
9 . The system of claim 8 , wherein eager-fetching the first data field comprises retrieving the data associated with the first data field.
10 . The system of claim 8 , wherein lazy-fetching the second data field comprises retrieving a reference link associated with the second data field.
11 . The system of claim 8 , further comprising:
in response to determining that the client is not associated with the second authentication tier, causing an authentication request associated with the second authentication tier to be issued to the client.
12 . The system of claim 11 , further comprising:
in response to determining that the client has satisfied the authentication requirements associated with the second authentication tier, retrieving the data associated with the second data field.
13 . The system of claim 11 , wherein the registry information references a plurality of authentication tiers, wherein each authentication tier is associated with a set of authentication requirements.
14 . The system of claim 11 , wherein the identifier associated with each resource is a URL.
15 . 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.
16 . The non-transitory media of claim 15 , wherein eager-fetching the first data field comprises retrieving the data associated with the first data field.
17 . The non-transitory media of claim 15 , wherein lazy-fetching the second data field comprises retrieving a reference link associated with the second data field.
18 . The non-transitory media of claim 15 , further comprising:
in response to determining that the client is not associated with the second authentication tier, causing an authentication request associated with the second authentication tier to be issued to the client.
19 . The non-transitory media of claim 18 , further comprising:
in response to determining that the client has satisfied the authentication requirements associated with the second authentication tier, retrieving the data associated with the second data field.
20 . The non-transitory media of claim 15 , wherein the registry information references a plurality of authentication tiers, wherein each authentication tier is associated with a set of authentication requirements.