During the onboarding process, I’m getting an invalid digital signature error during the compliance check. It was working fine until yesterday. @Ankit.K.Tiwari @Majd_Alawadi
1 Like
Hi,
We also have noted a downgraded performance of compliance-check APIs in production @Ankit.K.Tiwari
Hi @asyed4u ,
We have started receiving the same. This is the exact error:
[{"type":"ERROR","code":"invalid-digital-signature","category":"SIGNATURE_ERRORS","message":"Invalid digital signature","status":"ERROR"}]
How we should handle it? Everything was working as expected before.
Same for us, this is working in simulation, error is only for Production.
Isn’t the purpose of simulation to test our system is working perfectly ? But then why would this happen ?
@shiyaf_texol @pmohdameen @asyed4u you need to share details on sp_support@zatca.gov.sa or E-invoicing@zatca.gov.sa
2 Likes
you need to use new New certificate and key from new SDK , i faced same issue today , after update the certificate from new SDK , it work fine ..
I am having the same issue, even though I already used the same project/app to onboard other clients before
But this is happening today
We are not using any SDK, we have our custom solution as per the shared processes.
We could atleast identify if the issue is on our side or not if the issue comes up in simulation or development endpoints, but this is not the case. We have the issue only in production.
Same thing with us, the issue is only on Production
1 Like
Does anyone found the solution ?
@Ankit.K.Tiwari @Majd_Alawadi @idaoud as per below post from @mhmd_almalki and his question is not related to the SDK user, as there is no issue on that side. The concern lies with the custom solution system. Since he has already followed the signed documentation, we kindly request timely assistance to help him resolve this matter
@pmohdameen @sergei.shishov @shiyaf_texol @mojtaba @housunus @mhmd_almalki Two methods need to be reviewed: one for generating the digital signature and another for verifying the digital signature. These should be compared with the SDK code to ensure alignment and consistency. (…even though we followed the prior documentation steps)
The issue has been resolved. Please try again and inform us if you experience any further issues.
The issue has been resolved. Please try again and inform us if you experience any further issues.
1 Like
is the problem from server side, so we don’t need to change our code?
Dear mehamada,
Leave everything as it is.
Hi, as per my understanding, no need to change anything on our side.
Dear hnatividad,
yes, there’s no need to change anything.
1 Like