WebSocket API: Problems using cookie based authentication (C#)

Hi
I am having issues using cookie-based authentication, when opening the web socket connection to wss://emea-1-t2.streaming-pricing-api.refinitiv.com:443/WebSocket. I am developing my application in C# against .Net 5.0 using the WebSocketSharp library.
Assume I have a valid access token/refresh token pair acquired from the authentication server https://api.refinitiv.com/auth/oauth2/v1/token, i.e.
{
"access_token":"eyJ0e****effg",
"refresh_token": "****-def6-47b3-aeb2-1468796846b5",
"expires_in": "300",
"token_type": "Bearer"
}
Request based
I can successfully authenticate using a Login request as the initial request on the form:
{
"Domain":"Login",
"ID":1,
"Key":{
"Elements":{
"ApplicationId":"256",
"AuthenticationToken":"aBcDeFgHiJkLmNoPqRsTuVwXyZ",
"Position":"127.0.0.1"
},
"NameType":"AuthnToken"
}
}
This means I get a repsonse stating that the data is streaming etc., and I can perform additional requests.
Cookie based
The story is different, when I try to use cookie based authentication. The feature is described in the Protocol Specification page 18, where one can supply the below HTTP cookies, before connecting:
*ads*authTokenName : AuthToken
*ads*positionName : position
*ads*applicationIdName : applicationId
No matter what I do, I am not able to authenticate using this method. I have tried different ApplicationIds and positions. My code for this part is:
WebSocket.SetCookie(new Cookie("*ads*authTokenName", access_token));
WebSocket.SetCookie(new Cookie("*ads*positionName", position));
WebSocket.SetCookie(new Cookie("*ads*applicationIdName", "256"));
First of all, the example application provided here uses som completely different header names, i.e. AuthToken, AuthPosition, and applicationId. They seem more legit, than those in the protocol specification, but nevertheless, it doesn't work.
Whenever I try to perform a request (not Login request) after the connection, I am met with the following exception, after which the connection terminates:
Received Log Event (Level: Fatal): WebSocketSharp.WebSocketException: The header of a frame cannot be read from the stream.
at WebSocketSharp.WebSocketFrame.processHeader(Byte[] header)
at WebSocketSharp.WebSocketFrame.<>c__DisplayClass73_0.<readHeaderAsync>b__0(Byte[] bytes)
at WebSocketSharp.Ext.<>c__DisplayClass48_0.<ReadBytesAsync>b__0(IAsyncResult ar)
- Is cookie-based even possible?
- If so, which header names and values should I provide?
- Bonus question: Am I right in the assumption, that the token does not need to be refreshed, when application as a cookie? I not, what is the recommended method for refreshing it?
Best Answer
-
Hello @Kenneth Gabriel Birkedahl
I think the cookie-based authentication in the WebSocket API document means the deployed RTDS scenario that the application connects to a local ADS server, not the RTO (Refinitiv Real-Time Optimized) scenario which is over the cloud (currently AWS).
You can check the RTO scenario implementation detail from the Refinitiv Real-Time - Optimized Install and Config Guide document page (Section 2.8 "Consume Refinitiv Real-Time - Optimized Service")
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 684 Datastream
- 1.4K DSS
- 614 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 248 ETA
- 552 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 640 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 191 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛