<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<div>Sounds about right with my vendor experience thus far. Our main SPs are things like Lynda, Zimride, PBSvideo, Terradotta, and a few others.</div>
<div><br>
</div>
<div>To make sure I understand what you mentioned from before, you're saying I should add something like this and only this to the metadata? :</div>
<div><br>
</div>
<div><ArtifactResolutionService Binding="urn:oasis:names:tc:SAML:2.0:bindings:SOAP" Location="<a href="https://itfederation.jmu.edu:8443/idp/profile/SAML2/SOAP/ArtifactResolution">https://itfederation.jmu.edu:8443/idp/profile/SAML2/SOAP/ArtifactResolution</a>"
index="2"/></div>
<div><br>
</div>
<div> Thanks,</div>
<div><br>
</div>
<div>Brandon</div>
<div><br>
</div>
<div>On Wed, 2015-07-22 at 17:56 +0000, Cantor, Scott wrote:</div>
<blockquote type="cite">
<pre>On 7/22/15, 1:53 PM, "users on behalf of McKean, Brandon Scott - mckeanbs" <<a href="mailto:users-bounces@shibboleth.net">users-bounces@shibboleth.net</a> on behalf of <a href="mailto:mckeanbs@jmu.edu">mckeanbs@jmu.edu</a>> wrote:
<blockquote type="cite">
Since we already intend to have a discussion with service providers regarding required attributes, do you think it'd be appropriate to discuss their SAML2 support as part of that? Or is this something most providers are going to have no clue about?
</blockquote>
Most of them are on SAML 2 now and won't understand what you're asking, or will have it documented. That's about the only thing they document half the time.
Truth is, I don't know who you have in mind. In my experience, vendors don't handle metadata more often than not, so this doesn't come up in that context. If they do, I point them to InCommon's metadata, I don't give them metadata myself. Maybe that's the point here. Whether they're in InCommon is really irrelevant, that's where my metadata is for external consumption.
-- Scott
</pre>
</blockquote>
</body>
</html>