When signing SAML core impls, callers shouldn't add a SAMLObjectContentReference...
authorputmanb <putmanb@ab3bd59b-922f-494d-bb5f-6f0a3c29deca>
Fri, 24 Aug 2007 20:19:38 +0000 (20:19 +0000)
committerputmanb <putmanb@ab3bd59b-922f-494d-bb5f-6f0a3c29deca>
Fri, 24 Aug 2007 20:19:38 +0000 (20:19 +0000)
commit04101bb6f4e015adf59caec42ca9d0a7197533eb
treec3243af9370d3aadf906fc1b00cb9f081f6a3ef0
parentd4aa37d60872b1689fe896e81b22a6a64537edcd
When signing SAML core impls, callers shouldn't add a SAMLObjectContentReference, as this is already being handled
by the AbstractSignableSAMLObject impl.  Doing so results in redundant, duplicate References in the resulting signature.

git-svn-id: https://subversion.switch.ch/svn/shibboleth/java-idp/trunk@2350 ab3bd59b-922f-494d-bb5f-6f0a3c29deca
src/edu/internet2/middleware/shibboleth/idp/profile/saml1/AbstractSAML1ProfileHandler.java
src/edu/internet2/middleware/shibboleth/idp/profile/saml2/AbstractSAML2ProfileHandler.java