<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">On 10/22/23 3:31 PM, José Ramalho
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:d3186450a13342e89ff21298112c3431@ua.pt">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style>@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}div.WordSection1
{page:WordSection1;}</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1"><o:p></o:p>
<p class="MsoNormal">For my surprise, the validation failed
because my SingleSignOnService Bindings are declared before
the SingleLogoutService Binding.
<o:p></o:p></p>
<p class="MsoNormal">In terms of SAML is this order relevant? <o:p></o:p></p>
</div>
<br>
</blockquote>
<p><br>
</p>
<p>In terms of XML schema validity, yes the order in this particular
case is relevant. I don't personally know whether samltest.id is
performing full schema validation per se, but sounds like they are
at least checking the schema-defined order.</p>
<p>You can consult the saml-schema-metadata-2.0.xsd from the SAML
2.0 spec if you want it straight from the source, but a quick
summary is that in an IDPSSODescriptor the order of child elements
has to be like below. Order of child elements doesn't always
matter in schema - depends on how it's written - but in this
metadata case the elements are all in an ordered <sequence>.<br>
</p>
<p><font face="monospace"><!-- From SSODescriptorType --><br>
<element ref="md:ArtifactResolutionService" minOccurs="0"
maxOccurs="unbounded"/><br>
<element ref="md:SingleLogoutService" minOccurs="0"
maxOccurs="unbounded"/><br>
<element ref="md:ManageNameIDService" minOccurs="0"
maxOccurs="unbounded"/><br>
<element ref="md:NameIDFormat" minOccurs="0"
maxOccurs="unbounded"/><br>
</font></p>
<p><font face="monospace"><!-- From IDPSSODescriptorType --><br>
<element ref="md:SingleSignOnService"
maxOccurs="unbounded"/><br>
<element ref="md:NameIDMappingService" minOccurs="0"
maxOccurs="unbounded"/><br>
<element ref="md:AssertionIDRequestService" minOccurs="0"
maxOccurs="unbounded"/><br>
<element ref="md:AttributeProfile" minOccurs="0"
maxOccurs="unbounded"/><br>
<element ref="saml:Attribute" minOccurs="0"
maxOccurs="unbounded"/></font><br>
<br>
</p>
<p><br>
</p>
</body>
</html>