Verification Problem about xades4j

[GoogleCodeExporter]

Hi,

At a first glance the signature looks ok. I'll try to reproduce the issue later.

Original comment by luis.fgoncalv on 10 Aug 2011 at 8:52

[GoogleCodeExporter]

I'm waiting for your comments.
Thanks again.

Original comment by [email protected] on 11 Aug 2011 at 10:23

[GoogleCodeExporter]

I was able to sign the document and produce a signature identical to yours with 
the following code (uses helper methods on the lib test classes):

    class TestAlgsProvider extends DefaultAlgorithmsProvider
    {
        @Override
        public String getDigestAlgorithmForDataObjsReferences()
        {
            return MessageDigestAlgorithm.ALGO_ID_DIGEST_SHA1;
        }

        @Override
        public String getSignatureAlgorithm(String keyAlgorithmName) throws UnsupportedAlgorithmException
        {
            return XMLSignature.ALGO_ID_SIGNATURE_RSA_SHA1;
        }
    }

    /***************************************************************************/

        XadesBesSigningProfile profile = new XadesBesSigningProfile(keyingProviderMy);
        profile.withSignaturePropertiesProvider(new SignaturePropertiesProvider()
        {
            @Override
            public void provideProperties(SignaturePropertiesCollector signedPropsCol)
            {
                signedPropsCol.setSigningTime(new SigningTimeProperty());
                signedPropsCol.setSignerRole(new SignerRoleProperty("Test Role"));
            }
        })
        .withAlgorithmsProvider(TestAlgsProvider.class);

        Enveloped env = new Enveloped(profile.newSigner());

        Document doc = getDocument("test.xml");
        env.sign(doc.getDocumentElement());
        outputDocument(doc, "test_signed.xml");

        /***********************************************************************/

        XadesVerificationProfile verifProfile = new XadesVerificationProfile(VerifierTestBase.validationProviderMySigs);
        XadesVerifier verifier = verifProfile.newVerifier();

        doc = getDocument("test_signed.xml");
        Element signatureNode = VerifierTestBase.getSigElement(doc);
        verifier.verify(signatureNode, null);

If, on your scenario, the reference's digest changed, something is probably 
changing the dom tree after signature production.. How are you writing the 
signed file to disk?

Original comment by luis.fgoncalv on 14 Aug 2011 at 9:50

Attachments:

• test_signed.xml

[GoogleCodeExporter]

I was using my own xml save method. When i changed to your outputDocument and 
getDocument methods the problem was solved.

Thanks a lot for your help :)

Original comment by [email protected] on 15 Aug 2011 at 4:14

[GoogleCodeExporter]

Original comment by luis.fgoncalv on 16 Aug 2011 at 8:46

• Changed state: Invalid

[santipineda]

Hi;
I use xades4j for signing xml docs.
I'm signing the face_f0900032774003A699D2F.xml(attached) with xades4j with Xades-BES Enveloped type and produce face_f0900032774003A699D2F_signed.xml (attached).
But when my provider verifying xml signnature, show me this:

xades4j.verification.ReferenceValueException: Reference '#xmldsig-7786ae15-dcbf-46ff-94c6-d9c6834b9b25-keyinfo' cannot be validated

Please help!!!
face_f0900032774003A699D2F.zip

[Niedowidek]

Thank you very much. I made the same mistake (with writing signed xml to disk). This thread let me understand what I was doing wrong.

[FuriosoJack]

@santipineda Llegaste a solucionarlo?