Confirm transactions using the Hanko FIDO UAF Client

The process for confirming transactions with the Hanko FIDO UAF Client is essentially the same as for the regular authentication process. The main difference between the two is that when initializing the request you need to supply a request body with an additional transaction attribute. Its value is a transaction text that becomes part of the challenge issued by the FIDO server and hence the signature created in the course of the authentication process.

http POST {API_URL}/v1/uaf/requests \
 'Authorization:secret pasteYourApiKeySecretHere' \
 'operation=AUTH' \
 'username=example@example.com' \
 'userId=exampleId' \
 'transaction=Transfer $100 to Mike?'

curl -X POST "{API_URL}/v1/uaf/requests" \
-H 'Authorization:secret pasteYourApiKeyHere' \
-H 'Content-Type: application/json' \
-d '{"operation": "AUTH", "username":"example@example.com", "userId":"exampleId", "transaction": "Transfer $100 to Mike?" }'

Once the request has been initiated, pass it to the Hanko FIDO UAF Client and send the response back to the Hanko API exactly as described in the authentication guide.

Authentication De-registration

Getting started

Quickstarts

Guides

SDKs & Plugins

API Reference

Confirm transactions using the Hanko FIDO UAF Client