Signing authN question

[Mike Flynn]

Every now and then an IDP will ask us to sign authN for them and we will add a relying party rule to facilitate this like this:
<RelyingParty Name="http://entityId.com" signing ="true"/>   

And everything works fine. I had a request recently for this and added the rule but the customer says that it is not signing the authN.
In their metadata, we see this:
<md:EntityDescriptor xmlns:md="urn:oasis:names:tc:SAML:2.0:metadata" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" entityID="http://test-learning-admin-palfinger.cloudapp.net/idp"><md:IDPSSODescriptor WantAuthnRequestsSigned="true" protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">

And the rule defined for them is this:
  <RelyingParty Name="http://test-learning-admin-palfinger.cloudapp.net/idp" signing ="true"/>   

Maybe I am just old and blind but I cannot see anything that would prevent the signing from occurring. Can anyone offer any insight here?
Thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20170401/6fcc4bb6/attachment.html>