Issue with login to new RO account using v2 auth

I'm having an issue logging into my new RTO service account using v2 authentication and my Refinitiv representative asked me to post a question here.
If this is the wrong forum for this question, could you direct me to where I should inquire ?
I'm trying to connect using a Eta C consumer application.
Ad s a sanity test, I've also tried loggin in with the RTSDK WL consumer example application.
With the WL consumer example I use these options
./WatchlistConsumer -clientId <my client id> -clientSecret <my secret> -h eu-west-1-aws-3-sm.optimized-pricing-api.refinitiv.net -p 14002 -s ELEKTRON_DD -c encrypted -x
and I get this message
<!-- End Message (Channel IPC descriptor = 7) -->
<!-- Incoming Message (Channel IPC descriptor = 7) -->
<!-- Time: 17:32:57:147 -->
<!-- rwfMajorVer="14" rwfMinorVer="1" -->
<statusMsg domainType="RSSL_DMT_LOGIN" streamId="1" containerType="RSSL_DT_NO_DATA" flags="0x28 (RSSL_STMF_HAS_MSG_KEY|RSSL_STMF_HAS_STATE)" dataState="RSSL_DATA_SUSPECT" streamState="RSSL_STREAM_CLOSED" code="RSSL_SC_DACS_USER_ACCESS_TO_APP_DENIED" text="Authentication failed (1026, Request for token validation failed:Authentication server returned response code:400)." dataSize="0">
<key flags="0x6 (RSSL_MKF_HAS_NAME|RSSL_MKF_HAS_NAME_TYPE)" name="dev" nameType="1"/>
<dataBody>
</dataBody></statusMsg>
<!-- End Message (Channel IPC descriptor = 7) -->
Domain: RSSL_DMT_LOGIN
Stream: 1 Msg Class: RDM_LG_MT_STATUS
State: Closed/Suspect/Application is denied access to system - text: "Authentication failed (1026, Request for token validation failed:Authentication server returned response code:400)."
UserName: dev
Best Answer
-
Hello @andy.sciascia
The "Authentication failed (1026, Request for token validation failed:Authentication server returned response code:400)." error message indicates there is the authentication issue with the RDP service (RTO uses the RDP Authentication service).
I can run the WatchlistConsumer example connects to RTO with the following command:
-clientId <client_id> -clientSecret <client_secret> -sessionMgnt -c encrypted -ec socket -s ELEKTRON_DD -mp THB= -h <RTO endpoint> -p 14002 -restEnableLog -restLogFileName restlog.txt
Note: I am connecting to ap-northeast-1-aws-1-sm.optimized-pricing-api.refinitiv.net endpoint.
Result:
Can you retry with the parameters like me above?
If the problem persists, please enable the rest log file and share the rest log when then problem occurs.
- Do not forget to remove your credentials from the file before posting!)
The log file will be available on the application folder as follows:
Example log:
REST log redirected to file.
--- REST REQUEST ---
<!-- Time: 15:11:11:185 -->
URL: https://api.refinitiv.com/auth/oauth2/v2/token
HTTP method: POST
HTTP header data:
Content-Type : application/x-www-form-urlencoded
User-Agent : RTSDK
HTTP body data: grant_type=client_credentials&scope=trapi.streaming.pricing.read&client_id={clientid}
Request timeout: 90
--- REST RESPONSE ---
<!-- Time: 15:11:11:959 -->
HTTP header data:
Date : Thu, 07 Dec 2023 08:11:07 GMT
Content-Type : application/json
Content-Length : 90
Connection : keep-alive
X-Amzn-Trace-Id : Root=1-65717e1a-0a18df025a8cfa33198c3526
X-Served-By : region=ap-southeast-1; cid=79337fc004204a0a96fb0451d04855e6
X-Tr-Requestid : c942bcf3-2c41-46f5-9319-48c4655452e0
HTTP body data: { "expires_in":7199, "token_type":"Bearer", "access_token":"XXXXX"}
Protocol version: HTTP/1.1
HTTP status code: 200Alternatively, you may verify your RTO version 2 account credentials from the following cURL command:
curl -X POST \
'https://api.refinitiv.com:443/auth/oauth2/v2/token' \
--header 'Accept: */*' \
--header 'Authorization: Bearer ' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'client_secret={client secret}' \
--data-urlencode 'client_id={client id}' \
--data-urlencode 'grant_type=client_credentials' \
--data-urlencode 'scope=trapi'0
Answers
-
Hi. The login is working today.
State: Open/Ok/None - text: "Login accepted by host ads-fanout-sm-az2-euw1-prd."
It worked with my app unchanged - so I think that something got enabled overnight.
With the Watchlist app I had to specify -sessionMgnt for it to work.
I'm having an issue accessing data now but my Refinitiv account contact is looking into that. It may be timing as well. The license has just changed from pending to assigned but I may have to wait a bit longer to access data.
0 -
I'm happy for this issue to be closed. There was no code issue - just a setup that wasn't complete and an extra option I needed for the test tool.
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
- 690 Datastream
- 1.5K DSS
- 629 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 560 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 281 Open PermID
- 46 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 724 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
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 95 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛