Closed NabinKawan closed 4 months ago
@NabinKawan This is an example of the implementation of the login function, where for the payload we send an identifier that is a change address and a signData object. Have you tried this?
@teske00 The error is generated from the backend side. On the frontend, I am using cardano-test-wallet, which is a wallet we have implemented for our tests. The curl request mentioned in the ticket is request made by frontend using the login function you specified.
My question is, the error message is unclear. I have already implemented the signData logic in cardano-test-wallet
. Could you please help clarify what is causing this failure?
We have updated the backend, try again and let us know what response you get
{"data":null,"error":{"status":400,"name":"ApplicationError","message":"Verification failed","details":{}}}
It is still unclear, Login failed
has been changed to Verification failed
. Could you provide the error log on signature above?
In fact, the response returns what the problem is, and the problem is that the signDate verification did not pass
@NabinKawan Is this enough, can we close the issue?
Yes, it has been fixed and version of cardano-test-wallet has been updated. #1455
I've added support for wallet-based authentication for PDF in
cardano-test-wallet
. The authentication flow failed with the following error message:The error is unclear, making it hard to figure out the actual reason for failing.
Payload to sign:
Format of signature used:
For detailed information on the signing specification, refer to CIP-0008 signing spec.
Steps to reproduce: