Sending Correct Signature still the request is being nack

[Shreetej]

Even when verify_sign=false in config.yaml. The server is trying to verify the Header Authorization and sending Nack with
{
"message": {
"ack": {
"status": "NACK"
}
},
"error": {
"code": "20001",
"path": "string",
"message": "Cannot verify signature for request"
}
}

For push_receiver_recon
input payload - {
"context":{
"bpp_uri":"https://gateway.cept.gov.in/ondc",
"bpp_id":"gateway.cept.gov.in"
}
}

[logeshthiru]

Hi @Shreetej, Did you check verify_sign=false in the rsf/rsf.yaml file?

[Shreetej]

Hi Lokesh, Tried the same but still it didn't work. Had to change the keys. But now I am not receiving response to my reciever_recon after calling push_reciever_recon

…

On Fri, 15 Mar, 2024, 12:06 pm Logeshkumar t, ***@***.***> wrote: Hi @Shreetej <https://github.com/Shreetej>, Did you check verify_sign=false in the rsf/rsf.yaml file? — Reply to this email directly, view it on GitHub <#5 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AH55K3SERGBI2CH4A5GS3XLYYKJFXAVCNFSM6AAAAABC5RZOHCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJZGAZDQOJTGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>