Login request rejected, decoding failed
When attempting to log in with websockets RCC API, client is receiving
{"Stream":"ClosedRecover","Data":"Suspect","Code":"UsageError","Text":"Login request rejected, decoding failed"}}] LOG_INFO vtisprc 30.01.2023 07:26:02.753313 6224(520) Tr2Session[919] Status [Login]: Login request rejected, decoding failed
What would cause this error? Do we have any additional resources regarding this? Thanks
Best Answer
-
Hello @Ryan.Dowell
Did the application request the access token from the RDP API and send that token with the WebSocket Login message to RCC?
Basically, the application needs to send an HTTP Post request to RDP API first:
POST /auth/oauth2/v1/token HTTP/1.1
Accept: */*
Content-Type: application/x-www-form-urlencoded
Host: api.refinitiv.com:443
Content-Length: XXX
username=GEM-XXXXX
&password=XXXXXXX
&client_id=GEM-XXXXX
&grant_type=password
&takeExclusiveSignOnControl=trueThen, the RDP API sends the access token back to the application as a JSON message
{
"access_token": "<Access Token>",
"refresh_token": "XXXXXX",
"expires_in": "600",
"scope": "ZZZZZZZ",
"token_type": "Bearer"
}Next, the application establishes a connection to the RCC WebSocket server and sends the WebSocket Login request message to RCC with the access token. The JSON message format is as follows:
{
"Domain":"Login",
"ID":1,
"Key":{
"Elements":{
"ApplicationId":"256",
"AuthenticationToken":"<Access Token>",
"Position":"Machine IP/Machine Hostname"
},
"NameType":"AuthnToken"
}
}The client can find more detail about RCC and the WebSocket direct connection via this tutorial page.
Hope this helps.
1
Answers
-
Thanks for reaching out to us.
If the problem always happens, please share the login request message and the RCC hostname that the client is using. We will check the format of the login request message.
However, if the problem happens intermittently, please contact the Refinitiv Contributions Channel support team directly via MyRefinitiv. The error was sent by the RCC server so the support team may be able to check the cause of this error.
0
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 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
- 367 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
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛