Error invalid_grant when calling RDP APIs simultaneously

Hi Developer Advocate,
We are using RDP APIs with two user-ids for different services as follows:
- User 1: data-store/v1/graphql and discovery/symbology/v1/lookup, Approx time token first generated = 23:31, result = PASS
- User 2: alerts/v1/news-stories-subscriptions and data/news/v1/metadata, Approx time token first generated = 23:32, result = FAIL
Just to confirm the timeline of the issue:
- Generate a new access token for Filings
- Generate a new access token for News (a few milliseconds after Filings)
- After approx. 10 mins we refresh the news event token and this causes the job failure
- Filings continues to run and refresh logic seems to work ok for Filings (assume maybe as it was the first to establish a connection)
User 2 got the following errors:
23:40:28.282 [main] INFO RefinitivAPIConnection - Credentials provided, attempting to connect to https://api.refinitiv.com/auth/oauth2/v1/token:
23:40:29.175 [main] ERROR RefinitivAPIConnection - Error! No refresh token in response: {"error":"invalid_grant"}
Could you please advise what cause this issue and the next step?
Best Answer
-
Hello @John Martin
Thank for reaching out to us. The {"error":"invalid_grant"} error message is returned from the RDP APIs. It indicates that the application uses an invalidated refresh token with the refresh grant authentication.
Based on the Limitations and Guidelines for the RDP Authentication Service, each account has only one active session. A refresh token will be invalidated if other applications/sessions use the same account with the password grant authentication to get a new refresh and access token.
To verify User 2 account session when the problem occurred, I strongly suggest you contact the RDP support team directly to verify why the session got "invalid grant" error. You can contact the team via https://my.refinitiv.com/content/mytr/en/productsupport.html website.
Please note that if User 2 uses the same account for other RDP-related services (like the RTO) on the same time as RDP services, the applications may encounter an error when an access token expires or when the applications attempt to refresh an access token.
It is advisable to use multiple Machine-IDs/User-IDs if the client wants to run multiple applications/sessions.
I hope this information helps.
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
- 685 Datastream
- 1.4K DSS
- 616 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
- 252 ETA
- 557 WebSocket API
- 38 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
- 653 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
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 193 TREP Infrastructure
- 229 TRKD
- 917 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 中文论坛