Customer is moving from Machine IDs to Service IDs in RTO.

JakeDenley

Customer is moving from Machine IDs to Service IDs in RTO. They are getting the following error when trying to connect:

From application we do not have connectivity using params below. Params below have been used to initialize OmmConsumerConfig.

10:36:02,034 ERROR [com.fnx.service.adapter.refinitiv.JRefinitivAWSAgent] (pool-13-thread-3) JRefinitivAWSAgent: Failed to connect to Refinitiv ELEKTRON_DD Service. Caused by org/jose4j/lang/JoseException

10:36:07,041 INFO [com.refinitiv.ema.access.OmmConsumerImpl] (pool-13-thread-3) loggerMsg

ClientName: EmaConfig

Severity: Info

Text: Missing, unreadable or empty file configuration, path=[/of01/ironside/syb/lin/dev/domains/iristic-COPYDEV/EmaConfig.xml]

loggerMsgEnd

07 Nov 2024 08:43:03,848 INFO [ConfigTemplStaticConfigProcessor] ConfigTemplStaticConfigProcessor: Configuration [JRefinitivAWSAgent]: load parametar ClientSecret=***************

07 Nov 2024 08:43:03,849 INFO [ConfigTemplStaticConfigProcessor] ConfigTemplStaticConfigProcessor: Configuration [JRefinitivAWSAgent]: load parametar ServiceDiscoveryURL=

07 Nov 2024 08:43:03,849 INFO [ConfigTemplStaticConfigProcessor] ConfigTemplStaticConfigProcessor: Configuration [JRefinitivAWSAgent]: load parametar TokenURLV2=

07 Nov 2024 08:43:03,850 INFO [ConfigTemplStaticConfigProcessor] ConfigTemplStaticConfigProcessor: Configuration [JRefinitivAWSAgent]: load parametar ClientID=GE-36TO3ZZZMRYE

07 Nov 2024 08:43:03,851 INFO [ConfigTemplStaticConfigProcessor] ConfigTemplStaticConfigProcessor: Configuration [JRefinitivAWSAgent]: load parametar KeyStorePath=/syb/lin/dev/server/certs/aws/ref_keystore.jks

07 Nov 2024 08:43:03,852 INFO [ConfigTemplStaticConfigProcessor] ConfigTemplStaticConfigProcessor: Configuration [JRefinitivAWSAgent]: load parametar KeyStorePassword=***************

07 Nov 2024 08:43:03,852 INFO [ConfigTemplStaticConfigProcessor] ConfigTemplStaticConfigProcessor: Configuration [JRefinitivAWSAgent]: load parametar Service=ELEKTRON_DD

07 Nov 2024 08:43:03,852 INFO [ConfigTemplStaticConfigProcessor] ConfigTemplStaticConfigProcessor: Configuration [JRefinitivAWSAgent]: load parametar ProxyHost=10.49.98.4

07 Nov 2024 08:43:03,853 INFO [ConfigTemplStaticConfigProcessor] ConfigTemplStaticConfigProcessor: Configuration [JRefinitivAWSAgent]: load parametar ProxyPort=8080

We have connectivity from xterm using curl.

[linapp05 10:19]# curl -kv -x 10.49.98.4:8080 https://api.refinitiv.com

* Rebuilt URL to: 

* Trying 10.49.98.4...

* TCP_NODELAY set

* Connected to 10.49.98.4 (10.49.98.4) port 8080 (#0)

* allocate connect buffer!

* Establish HTTP proxy tunnel to http://api.refinitiv.com:443

> CONNECT http://api.refinitiv.com:443 HTTP/1.1

> Host: http://api.refinitiv.com:443

> User-Agent: curl/7.61.1

> Proxy-Connection: Keep-Alive

>

< HTTP/1.1 200 Connection established

<

* Proxy replied 200 to CONNECT request

* CONNECT phase completed!

* ALPN, offering h2

* ALPN, offering http/1.1

* successfully set certificate verify locations:

* CAfile: /etc/pki/tls/certs/ca-bundle.crt

CApath: none

* TLSv1.3 (OUT), TLS handshake, Client hello (1):

* CONNECT phase completed!

* CONNECT phase completed!

* TLSv1.3 (IN), TLS handshake, Server hello (2):

* TLSv1.3 (IN), TLS handshake, [no content] (0):

* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):

* TLSv1.3 (IN), TLS handshake, [no content] (0):

* TLSv1.3 (IN), TLS handshake, Certificate (11):

* TLSv1.3 (IN), TLS handshake, [no content] (0):

* TLSv1.3 (IN), TLS handshake, CERT verify (15):

* TLSv1.3 (IN), TLS handshake, [no content] (0):

* TLSv1.3 (IN), TLS handshake, Finished (20):

* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):

* TLSv1.3 (OUT), TLS handshake, [no content] (0):

* TLSv1.3 (OUT), TLS handshake, Finished (20):

* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256

* ALPN, server accepted to use h2

* Server certificate:

* subject: C=US; ST=New York; O=REFINITIV US LLC; CN=api.refinitiv.com

* start date: Jul 23 00:00:00 2024 GMT

* expire date: Jul 23 23:59:59 2025 GMT

* issuer: C=GB; ST=Greater Manchester; L=Salford; O=COMODO CA Limited; CN=COMODO RSA Organization Validation Secure Server CA

* SSL certificate verify ok.

* Using HTTP2, server supports multi-use

* Connection state changed (HTTP/2 confirmed)

* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0

* TLSv1.3 (OUT), TLS app data, [no content] (0):

* TLSv1.3 (OUT), TLS app data, [no content] (0):

* TLSv1.3 (OUT), TLS app data, [no content] (0):

* Using Stream ID: 1 (easy handle 0x55fbeb1dd620)

* TLSv1.3 (OUT), TLS app data, [no content] (0):

> GET / HTTP/2

> Host: api.refinitiv.com

> User-Agent: curl/7.61.1

> Accept: */*

>

* TLSv1.3 (IN), TLS handshake, [no content] (0):

* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):

* TLSv1.3 (IN), TLS app data, [no content] (0):

* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!

* TLSv1.3 (OUT), TLS app data, [no content] (0):

* TLSv1.3 (IN), TLS app data, [no content] (0):

* TLSv1.3 (IN), TLS app data, [no content] (0):

< HTTP/2 302

< server: awselb/2.0

< date: Thu, 07 Nov 2024 15:33:14 GMT

< content-type: text/html

< content-length: 110

< location: https://apidocs.refinitiv.com:443/

<

<html>

<head><title>302 Found</title></head>

<body>

<center><h1>302 Found</h1></center>

</body>

</html>

* Connection #0 to host 10.49.98.4 left intact

https://api.refinitiv.com/streaming/pricing/v1/https://api.refinitiv.com/auth/oauth2/v2/token https://api.refinitiv.com/

Gurpreet

Hello @JakeDenley,

Please have the client run the EMA example 113 with their new V2 credentials and verify that all the permissions and network paths are open and working.

Example - https://github.com/Refinitiv/Real-Time-SDK/tree/master/Java/Ema/Examples/src/main/java/com/refinitiv/ema/examples/training/consumer/series100/ex113_MP_SessionMgmt

They can then enable the REST API logs and RSSL logging and upload the log files here for us to look at an suggest.