Issue with Invalid Signed Properties Hashing in Simulator Mode (SignedProperties with id='xadesSignedProperties')

SDK, web-based validator and sandbox
1

Hi everyone,

I encountered an issue one week ago and, despite checking many articles, I haven’t found a solution yet. I’m hoping the community can help.

I’m working on an API integration that has been successfully completed in developer mode. However, when I moved to the simulator mode, I encountered the following error:

Invalid signed properties hashing, SignedProperties with id=‘xadesSignedProperties’

I believe this is related to the hashing of signed properties in the XAdES signature, but I am not sure where the issue lies. Has anyone else faced this error, and if so, how did you resolve it? Any insights or suggestions would be greatly appreciated!

Thank you in advance for your help!

2

If the tool you are using to sign the invoice works fine for the invoice you are reporting in the sandbox environment, then your problem is likely with the certificate you are using to sign the invoice in the simulation environment.

This is just my guess, From the error you mentioned, it should give the same error in the sandbox, because this error should occur due to an error in signing the invoice.

3

Dear @mubashirpalakkan

Thanks for reaching out,

Please note that the Data in sandbox portal it’s a dummy data, and it’s only to clarification the steps that you need to follow to ensure a successfully onboarding,

To ensure successfully onboarding you can do it through production or simulation environments only, during the fatoora portal, or fatoora simulation portal.

Knowing that you will need your RM access to the fatoora portal to be able to get the OTP even for simulation or production portal.

Thanks,
Ibrahem Daoud.

4

Here’s what I did in Fatoora Simulation Portal:

  1. Generated CSR: I created a CSR (Certificate Signing Request) using the company details.
  2. Generated OTP: I obtained the OTP through the onboarding process.
  3. API Call: I sent the API request via ComplianceInvoiceAPI.

Everything seemed to work fine until this point. The issue appears when the system tries to validate the signed properties, and it fails with the error related to the SignedProperties ID. I’m assuming this is tied to the XAdES signature process.