MDQ

[Christopher Bongaarts]

On 2/3/2021 12:17 PM, Donald Lohr wrote:
> So my read on this is, moving from the *md* url to the new *mdq* url 
> is all that is needed to move to the new mdq service, no matter how 
> you configure it.  The new *mdq* service supports (as document by 
> InCommon):
>
> a) caching the entries as needed by using DynamicHTTPMetadataProvider
> b) caching entries as needed by using DynamicHTTPMetadataProvider + 
> pre-fetching metadata for specific SPs by using 
> FileBackedHTTPMetadataProvider
> c) caching the entire aggregate by using 
> FileBackedHTTPMetadataProvider as supported via the md service
>
> Switching to the new mdq service is changing the url. Configuring for 
> the new mdq for any of its features (based on the needs of the 
> organization - with one of the above a-c options) is the second part. 
> While the two can be done together, they should not be married 
> together to exclusively mean or not mean switching to or not switching 
> to the new MDQ service.

I think this may reflect some terminological confusion of what "MDQ 
service" means.

My interpretation is that the "MDQ Service" refers specifically and 
exclusively to the per-entity Metadata Query Service that is consumed in 
Shib by the DynamicHTTPMetadataProvider.  This would also include the 
use of caching metadata for specific entities by using 
FileBackedHTTPMetadataProvider.

I would refer to the service that provides aggregates with an 
mdq.incommon.org URL as being an Aggregate Metadata service, which is 
consumed in Shib using a FileBackedHTTPMetadataProvider.  The fact that 
it happens to live on the same server URL as the actual per-entity MDQ 
Service is not really relevant.

-- 
%%  Christopher A. Bongaarts   %%  cab at umn.edu          %%
%%  OIT - Identity Management  %%  http://umn.edu/~cab  %%
%%  University of Minnesota    %%  +1 (612) 625-1809    %%

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20210203/f360112f/attachment.htm>