POST v1/cases/screeningRequest

suveer.singh

Hi

Receiving a 401 Unauthorised response on POST v1/cases/screeningRequest. I've successfully completed the request from POSTMAN, copied the date from the request and pasted into code to ensure request and signature generation are the same.

Please see requests below. This has been used only as a comparison :

//code

(request-target): post /v1/cases/screeningRequest
host: rms-world-check-one-api-pilot.thomsonreuters.com
date: Fri, 30 Aug 2019 08:57:10 GMT
content-type: application/json
content-length: 190
{
"groupId":"0a3687cf-6c28-1107-9b0a-4d0000000141",
"entityType": "INDIVIDUAL",
"providerTypes": [
"WATCHLIST"
],
"name": "putin",
"secondaryFields":[],
"customFields":[]
}

Signature keyId="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",algorithm="hmac-sha256",headers="(request-target) host date content-type content-length",signature="YG7EWwddhf0vw3KmVH3Bp35kks85O9k0LtkyCDlcHlU="

//postman

(request-target): post /v1/cases/screeningRequest
host: rms-world-check-one-api-pilot.thomsonreuters.com
date: Fri, 30 Aug 2019 08:57:10 GMT
content-type: application/json
content-length: 190
{
"groupId":"0a3687cf-6c28-1107-9b0a-4d0000000141",
"entityType": "INDIVIDUAL",
"providerTypes": [
"WATCHLIST"
],
"name": "putin",
"secondaryFields":[],
"customFields":[]
}

Signature keyId="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",algorithm="hmac-sha256",headers="(request-target) host date content-type content-length",signature="YG7EWwddhf0vw3KmVH3Bp35kks85O9k0LtkyCDlcHlU="

Based on the code above, the only value that changes when i send my request is the date. Copying the date between postman and code and modifying it by a minute yield the same result

suveer.singh

Finally found the issue, based on the request object having specific spaces in the content, turns out you cannot just serialize the content object into a json string and pass that through into the body. You literally have to build a string and pass that through. This is a rather unique solution