AlI am using the Postman standalone app, not the web extension. All calls fail with 401. I have also tried with the postman interceptor - installed interceptor bridge, the interceptor extension, and I can see that the interceptor is connected.
@jideobi.onuora
Thank you for your query.
Can you please provide us the console logs (Request/Response headers) of the API calls which are failing with Error 401? If you are using a chrome app, you would not be able to fetch the console logs. I would request you to please install the native postman Windows / Mac app so that you are able to fetch the console logs for the failed API call.
Prabhjyot.Mandla
GET /v1/groups HTTP/1.1
Date: Thu, 07 Nov 2019 06:18:07 GMT
Authorization: Signature keyId="2a63f5a6-e8c5-403d-9276-347bfff2b2ab",algorithm="hmac-sha256",headers="(request-target) host date",signature="La4G7RJRMqiRIZ9tXR68wB9Fk+eKN/nQnQZSvBMU/Vw="
User-Agent: PostmanRuntime/7.19.0
Accept: */*
Cache-Control: no-cache
Postman-Token: 12e62213-7f3b-420e-9b41-28333baa6c77
Host: rms-world-check-one-api-pilot.thomsonreuters.com
Accept-Encoding: gzip, deflate
Connection: keep-alive
HTTP/1.1 401 Unauthorized
X-Application-Context: application
Authorization: WWW-Authenticate: Signature realm="World-Check One API",algorithm="hmac-sha256",headers="(request-target) host date content-type content-length
Transfer-Encoding: chunked
Date: Thu, 07 Nov 2019 06:19:25 GMT
Server: ""
Connection: close
Thank you for sharing the details.
I see that there is a difference of more than 30 seconds between request date and response date timestamp in the headers. The time difference of 30 seconds is acceptable for a successful API call. Can you please adjust the system time to NTP and they re-try?
Please provide us the updated request and response headers along with the request body if you are still getting Error 401 after making the above suggested changes to assist you further.
