Need support for connecting to RTO v2

Hi,

I have to update the code of a software so that it supports RTO v2 (previously it was supporting RTO v1)

In RTO v1, I used to connect thanks to the following code:

    private OmmConsumer createOmmConsumer() {
        OmmConsumerConfig ommConsumerConfig = EmaFactory.createOmmConsumerConfig(configuration.getConfigurationFile());

        ommConsumerConfig.username(configuration.getUserName());
        ommConsumerConfig.position(configuration.getPosition());
        ommConsumerConfig.applicationId(configuration.getApplicationId().toString());
        ommConsumerConfig.password(configuration.getPassword());
        ommConsumerConfig.tunnelingKeyStorePasswd(configuration.getPassword());
        ommConsumerConfig.clientId(configuration.getClientId());

        return EmaFactory.createOmmConsumer(ommConsumerConfig, stateClient);
    }

I know that in RTO v2 the ommConsumerConfig should be configured differently

could you please send me an example?
do you confirm it should be something like that?

OmmConsumerConfig config = EmaFactory.createOmmConsumerConfig();

consumer  = EmaFactory.createOmmConsumer(config.consumerName("Consumer_1").clientSecret(credentials.clientSecret)
		        clientId(credentials.clientId).tokenServiceUrlV2(tokenUrlV2).config(configDb), oAuthCallback, (Object)credentials);

It seems that I need a clientSecret. I was given an access to the "LSEG Platform Administration" and I found account I want to use:

However, I don't know how to get/change the secret to be used?

Thanks for helping

Regards,

Philippe

Find more posts tagged with

java

refinitiv-realtime-sdk

#technology

RTO

Accepted answers

All comments

Gurpreet

Hello @philippe.mesmeur

Please see this EMA Session Management example which shows how to use the Client Credentials (v2) authentication. Its recommended that application should use Service Discovery before connecting to the streaming host, since the hosts can change and discovery will return the list which is based on user's license.

OmmConsumerConfig config = EmaFactory.createOmmConsumerConfig();
config.clientId("xxxxxxx");
config.clientSecret("xxxxxxx");
consumer  = EmaFactory.createOmmConsumer(config);

All other parameters like session management and the location of the streaming server can be specified in the EMAConfig.xml or programmatically.

If you are interested in providing programmatic config, then see this EMA example.

I would recommend that you run the examples before trying changes in your code. For account related questions like client ID, client secret etc, please reach out to your LSEG account manager.

Jirapongse

@philippe.mesmeur

You can also refer to the following articles:

wasin.w V3

Hello @philippe.mesmeur

There is also the EMA Consumer – Connecting to the Real-Time Optimized with Authentication Version 2 tutorial.

philippe.mesmeur

Hello,

If you are interested in providing programmatic config, then see this EMA example.
I would recommend that you run the examples before trying changes in your code. For account related questions like client ID, client secret etc, please reach out to your LSEG account manage

good idea; I tried to run the example with the following arguments:

./gradlew all runConsumer450 -PcommandLineArgs='-clientId REMOVED -clientSecret REMOVED'

(I'm currently still not sure of the validity of my password, I'm trying to get it from my admin… of course, I modified it in the example provided above 😜)

This command produces the following output:

Task :Ema:Examples:runconsumer450

Failed to query LDP service discovery. Error text: Failed to request authentication token information with HTTP error 401. Text: {"error":"invalid_client"  ,"error_description":"Invalid client or client credentials." }

Both hostname and port are not avaiable for establishing a connection with Real-Time - Optimized. Exiting...

Should I use it differently? Thanks for helping

Philippe

philippe.mesmeur

https://community.developers.refinitiv.com/discussion/comment/127985#Comment_127985

From EMA Consumer – Connecting to the Real-Time Optimized with Authentication Version 2

A client service. It is a password generated from the Platform Admin website. It is in this XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX format.

it seems that my password does not respect the expected format. I guess my password was generated when we were supporting RTO v1.

It seems to me that I have to regenerate it but I don't have the rights to do it: I contacted your administrator for that

Regards,

Philippe

Gurpreet

https://community.developers.refinitiv.com/discussion/comment/128018#Comment_128018

Your LSEG account manager can help with getting access/resetting the password. Please do not post the userID or password in these forums as the posts are public and can be read by all.

philippe.mesmeur

I was able to change the password from the "LSEG Platform Administration" from the "Application management" menu:

However, when running the command line (of course using my new password in the clientSecret parameter)

./gradlew runConsumer450 -PcommandLineArgs='-clientId REMOVED -clientSecret REMOVED'

I still get the following error message:

Failed to query LDP service discovery. Error text: Failed to request authentication token information with HTTP error 401. Text: {"error":"invalid_client"  ,"error_description":"Invalid client or client credentials." }
Both hostname and port are not avaiable for establishing a connection with Real-Time - Optimized. Exiting...

FYI, the value I use for the clientId parameter is the applicationName

wasin.w V3

Hello @philippe.mesmeur

The client-id of the V2 should be in GE-XXXXXXXXXXXX format (see https://developers.lseg.com/en/article-catalog/article/account-authorization-v1-to-v2-migration-cheat-sheet for more detail).

Could you please try the following cURL command to test your RTO version 2 credential?

curl --location 'https://api.refinitiv.com:443/auth/oauth2/v2/token' \

--header 'Content-Type: application/x-www-form-urlencoded' \

--header 'Authorization: ••••••' \

--data-urlencode 'client_secret={client_secret}' \

--data-urlencode 'client_id={client_id}' \

--data-urlencode 'grant_type=client_credentials' \

--data-urlencode 'scope=trapi'

philippe.mesmeur

I finally managed to connect to RTOv2; thanks for helping

FYI, once connected, I encountered another problem: so I opened another discussion:

https://community.developers.refinitiv.com/discussion/133094/assertion-when-trying-to-connect-to-rtov2

EXPLORE OUR SITES