<style>
/* Changing the layout to use less space for mobiles */
@media screen and (max-device-width: 480px), screen and (-webkit-min-device-pixel-ratio: 2) {
#email-body { min-width: 30em !important; }
#email-page { padding: 8px !important; }
#email-banner { padding: 8px 8px 0 8px !important; }
#email-avatar { margin: 1px 8px 8px 0 !important; padding: 0 !important; }
#email-fields { padding: 0 8px 8px 8px !important; }
#email-gutter { width: 0 !important; }
}
</style>
<div id="email-body">
<table id="email-wrap" align="center" border="0" cellpadding="0" cellspacing="0" style="background-color:#f0f0f0;color:#000000;width:100%;">
<tr valign="top">
<td id="email-page" style="padding:16px !important;">
<table align="center" border="0" cellpadding="0" cellspacing="0" style="background-color:#ffffff;border:1px solid #bbbbbb;color:#000000;width:100%;">
<tr valign="top">
<td bgcolor="#ffffff" style="background-color:#ffffff;color:#000000;font-family:Arial,FreeSans,Helvetica,sans-serif;font-size:12px;line-height:1;"><img src="https://shibboleth.net/images/shib_240x83.png" alt="" style="vertical-align:top;" /></td>
</tr><tr valign="top">
<td id="email-banner" style="padding:32px 32px 0 32px;">
<table align="left" border="0" cellpadding="0" cellspacing="0" width="100%" style="width:100%;">
<tr valign="top">
<td style="color:#505050;font-family:Arial,FreeSans,Helvetica,sans-serif;padding:0;">
<img id="email-avatar" src="https://issues.shibboleth.net/jira/secure/useravatar?avatarId=10202" alt="" height="48" width="48" border="0" align="left" style="padding:0;margin: 0 16px 16px 0;" />
<div id="email-action" style="padding: 0 0 8px 0;font-size:12px;line-height:18px;">
<a class="user-hover" rel="putmanb@shibboleth.net" id="email_putmanb@shibboleth.net" href="https://issues.shibboleth.net/jira/secure/ViewProfile.jspa?name=putmanb%40shibboleth.net" style="color:#326ca6;">Brent Putman</a>
commented on <img src="https://issues.shibboleth.net/jira/images/icons/issuetypes/bug.png" height="16" width="16" border="0" align="absmiddle" alt="Bug"> <a style='color:#326ca6;text-decoration:none;' href='https://issues.shibboleth.net/jira/browse/IDP-574'>IDP-574</a>
</div>
<div id="email-summary" style="font-size:16px;line-height:20px;padding:2px 0 16px 0;">
<a style='color:#326ca6;text-decoration:none;' href='https://issues.shibboleth.net/jira/browse/IDP-574'><strong>V2 to V3 upgraded IdP does not use algorithm agility metadata</strong></a>
</div>
</td>
</tr>
</table>
</td>
</tr>
<tr valign="top">
<td id="email-fields" style="padding:0 32px 32px 32px;">
<table border="0" cellpadding="0" cellspacing="0" style="padding:0;text-align:left;width:100%;" width="100%">
<tr valign="top">
<td id="email-gutter" style="width:64px;white-space:nowrap;"></td>
<td>
<table border="0" cellpadding="0" cellspacing="0" width="100%">
<tr valign="top">
<td colspan="2" style="color:#000000;font-family:Arial,FreeSans,Helvetica,sans-serif;font-size:12px;padding:0 0 16px 0;width:100%;">
<div class="comment-block" style="background-color:#edf5ff;border:1px solid #dddddd;color:#000000;padding:12px;"><p>For everyone else I'll repeat what Ian and I discussed privately in email: My read of the IdP code is that there really shouldn't be any differences here for a fresh vs upgraded install. I see what Rod is doing in the legacy parsing wrt synthetically creating a SecurityConfiguration for a <img class="emoticon" src="https://issues.shibboleth.net/jira/images/icons/emoticons/help_16.gif" height="16" width="16" align="absmiddle" alt="" border="0"/> ProfileConfiguration, containing a SignatureSigningConfiguration based on the legacy style signingCredentialRef, etc.</p>
<p>My observation though is that none of that should matter. For this case, the algorithm selection should be driven by metadata through the use of the SAMLMetadataSignatureSigningParametersResolver. AFAICT that resolver is being used unconditionally, so isn't affected by an upgrade vs not. With that resolver impl, as long as the resolver is passed the RoleDescriptor via the RoleDescriptorCriterion, the algorithm selection is (first) going to be driven by the metadata; only if there aren't algorithms there (or they aren't acceptable b/c of whitelist/blacklist policy or lack of runtime support) will the superclass logic which looks at the -Configuration instances be invoked. So whatever is being done with the -Configuration(s) should be irrelevant. </p>
<p>So the behavior Ian is reporting totally baffles me.</p>
<p>(Ian you never mentioned what your log output actually showed, with the 3 classes I mentioned on TRACE. Could you post that here? That will confirm that the SAMLMetadata- resolver is actually being used, and whether it's "seeing" the algorithms in metadata.)</p>
<p>The other weird thing is that for Ian it's signing with SHA-1. AFAIK, unless one messes with the default property toggles that Scott has in idp.properties, it should sign with SHA-256 by default. So that's also very puzzling.</p>
<p>I hate to ask the painfully obvious question, but: Ian is it possible that the SP metadata in question does in fact list SHA-1 algos first in its metadata? That's the only thing I can think of that is consistent with what you are seeing.</p>
<p>Since I have an upgraded IdP now, perhaps if you sent me a copy of the SP's full EntityDescriptor that your Idp has, I could plug that in to my IdP and see if I get the same or different result.</p></div>
<div style="color:#505050;padding:4px 0 0 0;"> </div>
</td>
</tr>
</table>
</td>
</tr>
</table>
</td>
</tr>
</table>
</td><!-- End #email-page -->
</tr>
<tr valign="top">
<td style="color:#505050;font-family:Arial,FreeSans,Helvetica,sans-serif;font-size:10px;line-height:14px;padding: 0 16px 16px 16px;text-align:center;">
This message is automatically generated by JIRA.<br />
If you think it was sent incorrectly, please contact your JIRA administrators<br />
For more information on JIRA, see: <a style='color:#326ca6;' href='http://www.atlassian.com/software/jira'>http://www.atlassian.com/software/jira</a>
</td>
</tr>
</table><!-- End #email-wrap -->
</div><!-- End #email-body -->