<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Thanks peter, that’s what I assumed.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I wish we could just use the incommon MDQ service, but in the infinite wisdom of this former maintainer we have two entity IDs one for incommon which only 5% of our SPs use and our primary which is fed by this custom aggregator/generator.
Yeah it’s a mess.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">--Joel <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">users <users-bounces@shibboleth.net> on behalf of Peter Schober via users <users@shibboleth.net><br>
<b>Date: </b>Thursday, April 28, 2022 at 4:28 PM<br>
<b>To: </b>users@shibboleth.net <users@shibboleth.net><br>
<b>Cc: </b>Peter Schober <peter.schober@univie.ac.at><br>
<b>Subject: </b>Re: signing IDP metadata<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal">*EXTERNAL EMAIL*<br>
<br>
* Herron, Joel D <herronj@uww.edu> [2022-04-28 23:12]:<br>
> The previous implementor of our IDP signed both of our<br>
> idp-metadata.xml files (standard and 4096 certs) with a custom xml<br>
> generator which I’m looking to retire.<br>
<br>
If you wanted to keep signing (see below9) you can always use<br>
XmlSecTool, <a href="https://shibboleth.atlassian.net/wiki/spaces/XSTJ3/overview">
https://shibboleth.atlassian.net/wiki/spaces/XSTJ3/overview</a><br>
or the SP's samlsign or other "non-custom" tools.<br>
<br>
> Is this a common practice? I’m not seeing anything in the<br>
> documentation that suggests that’s a something to even consider<br>
> doing. I can see the benefits in theory but that would require SPs<br>
> to actually check the signing.<br>
<br>
This. Also, you'd want to sign+expire[1] then, meaning you'd<br>
periodically (e.g. daily) add/set EntityDescrptor/@validUntil a few<br>
days/weeks into the future, sign and publish.<br>
<br>
But why self-publish your IDP's metadata at all? I.e., why not point<br>
the SP to the *signed*, constantly *updated* copy of your IDP's<br>
metadata in InCommon's MDQ service?<br>
<br>
> If I were to not sign it going forward I assume the risk would be if<br>
> some SP actually implemented the signing check it would fail for<br>
> them.<br>
<br>
Highly unlikey as that would break the service for all their<br>
non-signing customers (i.e., the other 99.9999%). ;)<br>
<br>
-peter<br>
-- <br>
For Consortium Member technical support, see <a href="https://shibboleth.atlassian.net/wiki/x/ZYEpPw">
https://shibboleth.atlassian.net/wiki/x/ZYEpPw</a><br>
To unsubscribe from this list send an email to users-unsubscribe@shibboleth.net<o:p></o:p></p>
</div>
</div>
</body>
</html>