<div>We have a requirement to use SHA256-based algorithms for SAML 2 signature and digest for communicating with an external IDP (possibly Shibboleth, but not positive).</div><div><br></div><div>I have been able to switch the signing algorithm very easily using the shibboleth2.xml signingAlg on the ApplicationDefault, ApplicationOverride and RelyingParty nodes.  I&#39;ve also been able to confirm that setting the shibboleth2.xml digestAlg will properly set the digest algorithm within a signature.</div>
<div><br></div><div>Where I am struggling is that a digest algorithm of SHA1 is consistently being used for the EncryptedKey within the EncryptedAssertion, EncryptedID, despite the digestAlg setting within the shibboleth2.xml</div>
<div><br></div><div>Is there any way to force this digest algorithm an SHA256 as well?  It seems to default to SHA1 regardless of value in digestAlg attribute.</div><div><br></div><div>Using Shibboleth SP 2.4.3 on Linux RHEL 5, 64-bit, OpenSaml 2.4.3, XML Tooling 1.4.2.</div>
<div><br></div><div>An example below:</div><div><br></div><div>&lt;samlp:LogoutRequest xmlns:samlp=&quot;urn:oasis:names:tc:SAML:2.0:protocol&quot;</div><div>                     Destination=&quot;<a href="https://idp.example.com/SAML2/Redirect/SLO">https://idp.example.com/SAML2/Redirect/SLO</a>&quot;</div>
<div>                     ID=&quot;_4fecc1e19c77c2beed48212b3f721968&quot;</div><div>                     IssueInstant=&quot;2012-04-17T16:47:08Z&quot;</div><div>                     Version=&quot;2.0&quot;&gt;</div><div>
    &lt;saml:Issuer xmlns:saml=&quot;urn:oasis:names:tc:SAML:2.0:assertion&quot;&gt;<a href="https://sp.example.com/Shibboleth">https://sp.example.com/Shibboleth</a>&lt;/saml:Issuer&gt;</div><div>    &lt;saml:EncryptedID xmlns:saml=&quot;urn:oasis:names:tc:SAML:2.0:assertion&quot;&gt;</div>
<div>        &lt;xenc:EncryptedData xmlns:xenc=&quot;<a href="http://www.w3.org/2001/04/xmlenc#">http://www.w3.org/2001/04/xmlenc#</a>&quot;</div><div>                            Type=&quot;<a href="http://www.w3.org/2001/04/xmlenc#Element">http://www.w3.org/2001/04/xmlenc#Element</a>&quot;&gt;</div>
<div>            &lt;xenc:EncryptionMethod Algorithm=&quot;<a href="http://www.w3.org/2001/04/xmlenc#aes128-cbc">http://www.w3.org/2001/04/xmlenc#aes128-cbc</a>&quot; /&gt;</div><div>            &lt;ds:KeyInfo xmlns:ds=&quot;<a href="http://www.w3.org/2000/09/xmldsig#">http://www.w3.org/2000/09/xmldsig#</a>&quot;&gt;</div>
<div>                &lt;xenc:EncryptedKey xmlns:xenc=&quot;<a href="http://www.w3.org/2001/04/xmlenc#">http://www.w3.org/2001/04/xmlenc#</a>&quot;&gt;</div><div>                    &lt;xenc:EncryptionMethod Algorithm=&quot;<a href="http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p">http://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p</a>&quot;&gt;</div>
<div>                        &lt;ds:DigestMethod Algorithm=&quot;<a href="http://www.w3.org/2000/09/xmldsig#sha1">http://www.w3.org/2000/09/xmldsig#sha1</a>&quot;</div><div>                                         xmlns:ds=&quot;<a href="http://www.w3.org/2000/09/xmldsig#">http://www.w3.org/2000/09/xmldsig#</a>&quot;/&gt;</div>
<div>                    &lt;/xenc:EncryptionMethod&gt;</div><div>                    &lt;xenc:CipherData&gt;</div><div>                        &lt;xenc:CipherValue&gt;.....&lt;/xenc:CipherValue&gt;</div><div>                    &lt;/xenc:CipherData&gt;</div>
<div>                &lt;/xenc:EncryptedKey&gt;</div><div>            &lt;/ds:KeyInfo&gt;</div><div>            &lt;xenc:CipherData&gt;</div><div>                &lt;xenc:CipherValue&gt;... ...&lt;/xenc:CipherValue&gt;</div>
<div>            &lt;/xenc:CipherData&gt;</div><div>        &lt;/xenc:EncryptedData&gt;</div><div>    &lt;/saml:EncryptedID&gt;</div><div>    &lt;samlp:SessionIndex&gt;8ebfb37e2afededc003df1cf741b7fc21cea1099c79280bad2dd264b6e651d25&lt;/samlp:SessionIndex&gt;</div>
<div>&lt;/samlp:LogoutRequest&gt;</div>