Simulation Portal Getting warning code: 'invalid-digital-signature" and "category":"SIGNATURE_ERRORS"'

FATOORA portal and Simulation portal
1

Getting new or unhandled error / warning code in our Simulation portal, PFB the details, Kindly advice, Recent days we have starting receiving this error.

{“validationResults”:{“infoMessages”:[{“type”:“INFO”,“code”:“XSD_ZATCA_VALID”,“category”:“XSD validation”,“message”:“Complied with UBL 2.1 standards in line with ZATCA specifications”,“status”:“PASS”}],“warningMessages”:[{“type”:“WARNING”,“code”:“invalid-digital-signature”,“category”:“SIGNATURE_ERRORS”,“message”:“The certificate in the invoice implies that it was signed with a private key different from the one associated with this device”,“status”:“WARNING”}],“errorMessages”:,“status”:“WARNING”}}

1 Like
2

you changed the private key after onboarding. you should keep it and not generate a new one maybe on each invoice

3

we are facing the same problem @Ankit.K.Tiwari any help is appreciated and the private key did not change

4

hi everyone,

same problem too ,

5

Dear Ankit.K.Tiwari,

Please let us know what we should do, all customers are complaining.

6

I Have Same Issues,
encountered the same problem again. The system now shows the following warning:

WARNING MESSAGE:
SIGNATURE_ERRORS
The certificate in the invoice implies that it was signed with a private key different from the one associated with this device.

Any help is appreciated. Please note that the private key has not changed

7

Currently we have started Receiving the same warning Error in ZATCA FATOORA PORTAL [PRODUCTION] Environment as well!. Please suggest the proper solution for this issue. Any help is appreciated. Thanks in advance

8

Same problem for us too. @Ankit.K.Tiwari

9

Hi dear community,

We have the same issue. It has started on Friday on simulation for some devices. But now it is happening much more often. Could we please know the reason of this error and how to fix it. I have checked, the certificate is still valid (this was my first assumption, that it got expired). We were reporting using the same codebase for 2 years without any warnings. And now it is returning 400 and the document is not reported:

{
    "validationResults": {
        "infoMessages": [
            {
                "type": "INFO",
                "code": "XSD_ZATCA_VALID",
                "category": "XSD validation",
                "message": "Complied with UBL 2.1 standards in line with ZATCA specifications",
                "status": "PASS"
            }
        ],
        "warningMessages": [],
        "errorMessages": [
            {
                "type": "ERROR",
                "code": "invalid-digital-signature",
                "category": "SIGNATURE_ERRORS",
                "message": "Invalid digital signature",
                "status": "ERROR"
            }
        ],
        "status": "ERROR"
    },
    "reportingStatus": "NOT_REPORTED"
}

@Ankit.K.Tiwari it would be nice to clarify the situation.

– Sergei