<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
<div class="moz-cite-prefix">On 5/21/15 8:30 AM, Cantor, Scott
wrote:<br>
</div>
<blockquote cite="mid:20ED38C8-DCB7-44A6-BCFE-16A001DD4264@osu.edu"
type="cite">
<pre wrap="">
</pre>
<pre wrap="">
Reason I asked is that's invalid. SAML extension containers like
Conditions require that the extension element by done via xsi:type, not
element name. </pre>
</blockquote>
<br>
You lost me, I didn't see anything in there re: Conditions. Are you
steps ahead and assuming that these things would have to be
represented in a protocol message or Assertion as Condition(s), and
then extrapolating? If so, that makes sense, but I think that's
throwing the OP off because I don't think that's literally why his
unmarshalling is failing. <br>
<br>
<br>
<blockquote cite="mid:20ED38C8-DCB7-44A6-BCFE-16A001DD4264@osu.edu"
type="cite">
<pre wrap="">And you're registering the *type*, not the element name.
</pre>
</blockquote>
<br>
I believe that's why it's currently failing.<br>
<br>
<br>
<blockquote cite="mid:20ED38C8-DCB7-44A6-BCFE-16A001DD4264@osu.edu"
type="cite">
<pre wrap="">
</pre>
That should be <saml:Condition
xsi:type="wso2:RequestedAudiences"> or whatever the typename
is. An element like that will be schema-invalid.</blockquote>
<br>
<br>
I'm not seeing why what he posted is schema-invalid. It may or may
not make sense from a design-a-SAML-metadata-extension perspective.<br>
<br>
<br>
<br>
<br>
<br>
</body>
</html>