search

mokth / einvoice

e-invoices sample files
40 stars 10 forks source link

Signed properties digest value doesn't match digest #3

Closed usha-cv closed 2 months ago

usha-cv commented 2 months ago

We tried signature xml invoice. but we got below response

"status": "Invalid", "error": { "propertyName": null, "propertyPath": null, "errorCode": "Error21", "error": "Document Signature Validator", "errorMs": "Document Signature Validator", "innerError": [ { "propertyName": "DigestValue", "propertyPath": "Invoice.UBLExtensions.UBLExtensions.ExtensionContent.UBLDocumentSignatures.SignatureInformation.Signature.SignedInfo.Reference@Type=\"http://uri.etsi.org/01903/v1.3.2#SignedProperties\".DigestValue", "errorCode": "DS320", "error": "Signed properties digest value doesn't match digest calculated value from provided signed properties section where ID is id-xades-signed-props.", "errorMs": "Nilai pencernaan sifat yang ditandatangani tidak sepadan dengan nilai pencernaan yang dikira dari bahagian sifat yang ditandatangani yang diberikan di mana ID adalah id-xades-signed-props.", "innerError": null } ] },

mokth commented 2 months ago

what language did u use?

gregorykau commented 2 months ago

Have you checked if any of the fields have double spaces e.g. "Lot 13" for a buyer address line? We have encountered something similar, it looks like IRBM may be performing additional white-space removal on the submitted XML before calculating the digest for comparison. The solution in our scenario was to remove double spaces in all text elements before calling the C# app.

mokth commented 2 months ago

yes, all string will be serialize to 1 line of string only. All this been mentioned in the einvoice SDK.

mokth commented 2 months ago

The json or xml serialization in my coding will auto do that.

From: Kian Gregory @.> Sent: 20 August 2024 11:27 To: mokth/einvoice @.> Cc: TH MOK @.>; Comment @.> Subject: Re: [mokth/einvoice] Signed properties digest value doesn't match digest (Issue #3)

Have you checked if any of the fields have double spaces e.g. "Lot 13" for a buyer address line? We have encountered something similar, it looks like IRBM may be performing additional white-space removal on the submitted XML before calculating the digest for comparison. The solution in our scenario was to remove double spaces in all text elements before calling the C# app.

— Reply to this email directly, view it on GitHubhttps://github.com/mokth/einvoice/issues/3#issuecomment-2297891162, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AABMID3UPFYG4T7OVRH6H3DZSKZS3AVCNFSM6AAAAABMVNNOHGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJXHA4TCMJWGI. You are receiving this because you commented.Message ID: @.***>