World Check One API giving Unauthorized 401 on server but working on local
Hi,
I am integrating WC1 in my project. It is working fine on my local system. But when i am running the API on server it is giving Unauthorized 401 for start GET Group APi. Is there any reasons of it?
Best Answer
-
I would like to update that it is working now. We did some server changes and responses are getting as expected. I will let you know if I face any issues.
Thanks for your help and assistance.
I appreciate your effort.1
Answers
-
Can you provide me the complete request and response headers , screenshot doesn't contain the complete signature , I would like to verify that further.
Thanks,
Mehran Khan
0 -
Here it is :
0 -
I woould like to verify your HMAC signature , can you please state your account name?
0 -
I verified the HMAC generated in your request and is correct that leaves us with the only thing, can you check the signature key ID in the request if it's correct and there are no extra spaces in there?
0 -
I have checked it and not sending any extra spaces in signature key ID. The same code is working fine on my local development environment, but not working on server.
Here is my response header :'GET /v1/groups HTTP/1.1\r\nAuthorization: Signature keyId="3*******************0",algorithm="hmac-sha256",headers="(request-target) host date",signature="5bqUQwyc9jp/UNF4RWNKqOumMFaNdDIylb+JpusKNWU="\r\nDate: Fri, 17 May 2019 12:57:52 GMT\r\nhost: rms-world-check-one-api-pilot.thomsonreuters.com\r\nConnection: close\r\n\r\n'
But not working?0 -
Let's get into a phone call tomorrow and take this discussion forward, let me the best suitable time for you I will send out an invite.
0 -
Hi, Can we meet today at 8:00 am PST.
Zoom Meeting Link: https://zoom.us/j/34173206470 -
Hi,
Apologies for the delayed response, we are available from 9 AM to 6 PM IST, Mon - Fri.
I guess it will be too early for you, I will be happy to stretch and take a call at 8 AM PST today , kindly confirm.
0 -
Hi,
Apologies for the delayed response, we are available from 9 AM - 6 PM IST, Mon- Fri.
I guess that will be too early for you, I will be happy to stretch and take a call at 8 am pst today, kindly confirm
0 -
I would like to update that it is working now. We did some server changes and responses are getting as expected. I will let you know if I face any issues.
Thanks for your help and assistance.
I appreciate your effort.0 -
1
-
I have one question after submitting a screening request({{protocol}}{{gateway-host}}{{gateway-url}}cases/{{case-system-id}}/screeningRequest) at least how much time it take to give screening result({{protocol}}{{gateway-host}}{{gateway-url}}cases/{{case-system-id}}/results)? As i am seeing it is giving after 10 seconds.
0 -
The screening request mentioned by you above is of the asynchronous screening, so when you place the screen request what the system does is it queues the request for screening as its asynchronous in nature and then screens it.
The response time depends on 3 parameters,
1. The name being screened - if you're screening a common name such as Mohammed, for example, the request would take longer time comparatively as the amount of data returned would be huge.
2. The load capacity of our platform.
3. Time is taken for the request to reach our servers and also the time taken for your systems to get the response.
Ideally, it shouldn't take much but I would suggest you perform adequate testing and derive the behavioural pattern.
Let me know if you need further information
0 -
what are those changes can u pls let me know,for also same issue its working in my local tomcat server but if i deploy in weblogic server its not working 401 error is getting. developed in rest api java0
Categories
- All Categories
- 6 AHS
- 39 Alpha
- 162 App Studio
- 4 Block Chain
- 5 Bot Platform
- 17 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 370 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 60 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛