<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 1/12/15 5:55 PM, Tom Scavo wrote:<br>
</div>
<blockquote
cite="mid:CAEtu=dMPNG+8PW4z_L_JkM88W8xidMYtEdcrvqLTAw8+OzqYfw@mail.gmail.com"
type="cite">
<pre wrap="">InCommon is preparing to announce a beta Metadata Query Server that
serves both per-IdP metadata and per-SP metadata. See the top of this
wiki page for more info: <a class="moz-txt-link-freetext" href="https://spaces.internet2.edu/x/3w7kAg">https://spaces.internet2.edu/x/3w7kAg</a></pre>
</blockquote>
<br>
Cool.<br>
<blockquote
cite="mid:CAEtu=dMPNG+8PW4z_L_JkM88W8xidMYtEdcrvqLTAw8+OzqYfw@mail.gmail.com"
type="cite">
<pre wrap="">
AFAICT there still is no documentation for the new
DynamicHTTPMetadataProvider. Can someone cobble together a wiki page
or at least give some hints how to do this?
</pre>
</blockquote>
<br>
<br>
I'd venture that any real solid docs are going to be a little
while. Scott or someone has some structure in place, but filling it
is still pending....<br>
<br>
For the moment, if you just want some quick and dirty examples, I
could point you to some basic unit test examples, as well as the
schema. The latter does have docs in it for what the various
parameters do - many are shared by all the providers, so need to
look at the type inheritance for
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
DynamicHTTPMetadataProvider and
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
AbstractDynamicHTTPMetadataProviderType, etc.<br>
<br>
<br>
Basic MDQ style of usage, with all default params:<br>
<br>
<a class="moz-txt-link-freetext" href="http://svn.shibboleth.net/view/java-identity-provider/trunk/idp-profile-spring/src/test/resources/net/shibboleth/idp/profile/spring/relyingparty/metadata/dynamicMetadataQueryProtocol.xml?revision=6930&view=markup">http://svn.shibboleth.net/view/java-identity-provider/trunk/idp-profile-spring/src/test/resources/net/shibboleth/idp/profile/spring/relyingparty/metadata/dynamicMetadataQueryProtocol.xml?revision=6930&view=markup</a><br>
<br>
As you can see there's not much to it. You give it the "base URL" as
defined by the spec (i.e. without the /entities on the end). For
the IdP 3.x, note that we have explicit support configuring MDQ (the
other 3 dynamic "modes" of usage are 1) template 2) regex and 3)
well-known location per the metadata spec). With the current SP
stuff, AFAIK you have to sort of cobble it together using the
<Subst> input and plugging in the entityID param, etc. No
need to do that in the IdP.<br>
<br>
<br>
<br>
<br>
Main non-default params for the dynamic provider in general:<br>
<br>
<a class="moz-txt-link-freetext" href="http://svn.shibboleth.net/view/java-identity-provider/trunk/idp-profile-spring/src/test/resources/net/shibboleth/idp/profile/spring/relyingparty/metadata/dynamicBasicParams.xml?revision=7083&view=markup">http://svn.shibboleth.net/view/java-identity-provider/trunk/idp-profile-spring/src/test/resources/net/shibboleth/idp/profile/spring/relyingparty/metadata/dynamicBasicParams.xml?revision=7083&view=markup</a><br>
<br>
<br>
<br>
All the extant examples of the dynamic provider are in this dir, the
ones that start with "dynamic..."<br>
<br>
<a class="moz-txt-link-freetext" href="http://svn.shibboleth.net/view/java-identity-provider/trunk/idp-profile-spring/src/test/resources/net/shibboleth/idp/profile/spring/relyingparty/metadata/">http://svn.shibboleth.net/view/java-identity-provider/trunk/idp-profile-spring/src/test/resources/net/shibboleth/idp/profile/spring/relyingparty/metadata/</a><br>
<br>
<br>
<br>
The IdP metadata config schema:<br>
<br>
<a class="moz-txt-link-freetext" href="http://svn.shibboleth.net/view/java-identity-provider/trunk/idp-schema/src/main/resources/schema/shibboleth-metadata.xsd?revision=7235&view=markup">http://svn.shibboleth.net/view/java-identity-provider/trunk/idp-schema/src/main/resources/schema/shibboleth-metadata.xsd?revision=7235&view=markup</a><br>
<br>
Hopefully most of the attributes are self-explanatory, or the doc
annotations are clear enough for the your short-term needs, but if
not, let me know and I'll elaborate.<br>
<br>
<br>
Hope that's enough to get you started until we have some real docs.<br>
<br>
--Brent<br>
</body>
</html>