<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 2/3/2021 12:17 PM, Donald Lohr
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:ce4674dd-ad49-670e-ef22-a95d424a1a88@jmu.edu"><span
class="sv-ti-done">So my read on this is, moving from the <b>md</b>
url to the new <b>mdq</b> url is all that is needed to move to
the new mdq service, no matter how you configure it. The new <b>mdq</b>
service supports (as document by InCommon):<br>
<br>
a) caching the entries as needed by using </span><span
class="sv-ti-done">DynamicHTTPMetadataProvider <br>
</span><span class="sv-ti-done">b) caching entries as ne</span>eded
by using DynamicHTTPMetadataProvider + pre-fetching metadata for
specific SPs by using FileBackedHTTPMetadataProvider<br>
<span class="sv-ti-done">
<style type="text/css">p { margin-bottom: 0.1in; direction: ltr; color: #000000; line-height: 115%; text-align: left; orphans: 2; widows: 2; background: transparent }p.western { font-family: "Liberation Serif", serif; font-size: 12pt; so-language: en-US }p.cjk { font-family: "Songti SC"; font-size: 12pt; so-language: zh-CN }p.ctl { font-family: "Arial Unicode MS"; font-size: 12pt; so-language: hi-IN }a:visited { color: #800000; so-language: zxx; text-decoration: underline }code.western { font-family: "Liberation Mono", serif }code.cjk { font-family: "Liberation Mono" }code.ctl { font-family: "Liberation Mono" }a:link { color: #000080; so-language: zxx; text-decoration: underline }</style>c)
caching the entire aggregate by using </span><span
class="sv-ti-done">FileBackedHTTPMetadataProvider as supported
via the md service<br>
<br>
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.</span></blockquote>
<p>I think this may reflect some terminological confusion of what
"MDQ service" means.</p>
<p>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.<br>
</p>
<p>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.<br>
</p>
<pre class="moz-signature" cols="72">--
%% Christopher A. Bongaarts %% <a class="moz-txt-link-abbreviated" href="mailto:cab@umn.edu">cab@umn.edu</a> %%
%% OIT - Identity Management %% <a class="moz-txt-link-freetext" href="http://umn.edu/~cab">http://umn.edu/~cab</a> %%
%% University of Minnesota %% +1 (612) 625-1809 %%
</pre>
</body>
</html>