Missing AuthenticationTTReissue field in Login response with Authentication V2
Hello,
We're using the Real-Time Optimized API via websockets. The login response elements container previously contained an 'AuthenticationTTReissue' value when using V1 authentication. This appears to be missing when using the new V2 authentication. I also don't see this value in the current API specification; can someone confirm that we will no longer receive a AuthenticationTTReissue value in the login response?
Thanks!
Will
Best Answer
-
Hi @wzimmerman,
The authentication mechanism and the way token used to expire has changed in v2 authentication. This field is still sent out in V1 response, but not in the v2 response because as long as your application is connected to the v2 auth session, the token does not need to be reissued.
0
Answers
-
Hello @wzimmerman
Like my colleague has mention, the application/API does not need to renew an Access Token (HTTP/RSSL-WebSocket) as long as the streaming channel (WebSocket/RSSL) is active with the Version 2 authentication.
The Version 2 authentication request-response messages HTTP structures are as follows:
Request:
POST /auth/oauth2/v2/token HTTP/1.1
Accept: */*
Content-Type: application/x-www-form-urlencoded
Host: api.refinitiv.com:443
Content-Length: XXX
client_id=KKKKKKKKKKKKKKKKKK
&client_secret=BBBBBBBBBBBBBBBBBBBB
&grant_type=client_credentialsResponse:
{
"expires_in": 7199,
"token_type": "Bearer",
"access_token": "YYYYYYYYYYYYY"
}where:
- access_token: The token used to invoke REST data API calls as described above. The application must keep this credential for further RDP APIs requests.
- expires_in: Access token validity time in seconds.
- token_type (required): The type of token this is, typically just the string “Bearer”.
You can find more detail about the Version 2 authentication on the following articles:
- Getting Started with Version 2 Authentication for Refinitiv Real-Time and Data Platform: Overview
- Real-Time WebSocket API: Refinitiv Real-Time Optimized Version 2 Authentication Migration Guide
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 中文论坛