Hello LSEG,
we're working to setup an application based on the EMA C++ library for connections towards RTO.
Context:
- the execution environment is currently under investigations (with some of you guys from LSEG) for some network issues preventing a complete communication with RTO
- recently, some issues have been resolved in order to allow V2 authentication towards RTO, via Delivery Direct
- the network setup is still under analysis for what regards the service discovery step
Let me focus on the authentication part.
We have been using a python sample based on the Refinitiv WebSocket API.
The sample can authenticate with success using the URL https://us-east-1-api.refinitiv.biz/auth/oauth2/v2/token (see attached material).
While the service discovery requirements are being analyzed from the networking point of view, we've tried to test the authentication step with an EMA based application and the same V2 URL.
However, it seems that the authentication step is not working, or at least we don't know how to determine whether it was successful or not from the output.
Please find in attachment the EmaConfig.xml file used for the test, and the log generated during the run.
Ps: we've also done the same test using:
- the Java sample based on the EMA library (https://developers.lseg.com/en/api-catalog/refinitiv-real-time-opnsrc/rt-sdk-java/tutorials#ema-consumer-connecting-to-the-real-time-optimized-with-authentication-version-2), but also this test failed.
- the Cons113 sample of the C++ SDK (with the libcurl library dll in the working directory, loaded successfully), but also this test failed.
What do you think might be the root cause of the issue?
Do the Python WebSocket API and the EMA (C or Java) APIs use different protocols or channels for authentication with RTO?
Do you see anything incorrect in the configuration used?
Anything else that we can check?
Some additional details:
- OS: Windows
- the EMA C++ library used is 3.8.1.L1
- the EMA Java library used is 3.8.0.0
- RSSL_HTTP as EncryptedProtocolType for all the tests based on EMA (C or Java)
- we initially tried with RSSL_SOCKET, getting then "Error: 0012 Unable to load openSSL Libraries."; by looking at previous threads like (https://community.developers.refinitiv.com/questions/51792/error-0012-unable-to-load-openssl-libraries.html), we understood that RSSL_HTTP should be used instead on Windows
Test material: auth-rto-tests.zip
Thanks,
Paolo