Could you please check from your end why error 404 is generated?

AlissaCarla

RTO - RTDS

takeExclusiveSignOnControl parameter has been included into connection parameters, and when the server log is started it is shown that added parameter is taken into account and that  is correctly set to true:

09 Sep 2025 11:03:26,409 INFO  [ConfigTemplStaticConfigProcessor] ConfigTemplStaticConfigProcessor: Configuration [JRefinitivAWSAgent]: load parametar ClientSecret=***************

09 Sep 2025 11:03:26,409 INFO  [ConfigTemplStaticConfigProcessor] ConfigTemplStaticConfigProcessor: Configuration [JRefinitivAWSAgent]: load parametar TokenURLV1=https://api.refinitiv.com/auth/oauth2/v1/token

09 Sep 2025 11:03:26,409 INFO  [ConfigTemplStaticConfigProcessor] ConfigTemplStaticConfigProcessor: Configuration [JRefinitivAWSAgent]: load parametar ServiceDiscoveryURL=https://api.refinitiv.com/streaming/pricing/v1

09 Sep 2025 11:03:26,410 INFO  [ConfigTemplStaticConfigProcessor] ConfigTemplStaticConfigProcessor: Configuration [JRefinitivAWSAgent]: load parametar TokenURLV2=

09 Sep 2025 11:03:26,410 INFO  [ConfigTemplStaticConfigProcessor] ConfigTemplStaticConfigProcessor: Configuration [JRefinitivAWSAgent]: load parametar TakeExclusiveSignOnControl=true

09 Sep 2025 11:03:26,410 INFO  [ConfigTemplStaticConfigProcessor] ConfigTemplStaticConfigProcessor: Configuration [JRefinitivAWSAgent]: load parametar Username=GE-A-00811626-3-8202

09 Sep 2025 11:03:26,410 INFO  [ConfigTemplStaticConfigProcessor] ConfigTemplStaticConfigProcessor: Configuration [JRefinitivAWSAgent]: load parametar Password=***************

09 Sep 2025 11:03:26,410 INFO  [ConfigTemplStaticConfigProcessor] ConfigTemplStaticConfigProcessor: Configuration [JRefinitivAWSAgent]: load parametar ClientID=dcea8bfffcd2450bbf1b2e861fcaed681eb5fb91

09 Sep 2025 11:03:26,410 INFO  [ConfigTemplStaticConfigProcessor] ConfigTemplStaticConfigProcessor: Configuration [JRefinitivAWSAgent]: load parametar KeyStorePath=/asp_APPL/AMXCBPDE/server/certs/aws/ref_keystore.jks

09 Sep 2025 11:03:26,410 INFO  [ConfigTemplStaticConfigProcessor] ConfigTemplStaticConfigProcessor: Configuration [JRefinitivAWSAgent]: load parametar KeyStorePassword=***************

09 Sep 2025 11:03:26,410 INFO  [ConfigTemplStaticConfigProcessor] ConfigTemplStaticConfigProcessor: Configuration [JRefinitivAWSAgent]: load parametar Service=ELEKTRON_DD

09 Sep 2025 11:03:26,410 INFO  [ConfigTemplStaticConfigProcessor] ConfigTemplStaticConfigProcessor: Configuration [JRefinitivAWSAgent]: load parametar ProxyHost=proxy-na.avantgard.corp

09 Sep 2025 11:03:26,411 INFO  [ConfigTemplStaticConfigProcessor] ConfigTemplStaticConfigProcessor: Configuration [JRefinitivAWSAgent]: load parametar ProxyPort=8080

 

From the current log with included TakeExclusiveSignOnControl attribute, we can see that we got a valid access token in HTTP response:

 

                The next HTTP response was received

                HTTP/1.1 200 OK

                                Date: Tue, 09 Sep 2025 14:29:04 GMT

                                Content-Type: application/json

                                Connection: keep-alive

                                X-Amzn-Trace-Id: Root=1-68c039af-7fe51f5b30a351260170aa40

                                X-Served-By: region=us-east-1; cid=7ea4577517d546ff9220d5f97a725e14

                                X-Tr-Requestid: 6d657056-3275-417d-9bbd-dd533671e44a

                                Content string:

                                                { "access_token":"eyJhbGciOiJSUzI1NiIsImtpZCI6ImRMdFd2Q0tCSC1NclVyWm9YMXFod2pZQ2t1eDV0V2ZSS2o4ME9vcjdUY28iLCJ0eXAiOiJhdCtqd3QifQ.eyJhdWQiOiJkY2VhOGJmZmZjZDI0NTBiYmYxYjJlODYxZmNhZWQ2ODFlYjVmYjkxIiwiZGF0YSI6IntcImNpcGhlcnRleHRcIjpcIjMyNld3WGlna3FrWXpUS0Z1d0ZOd2dfdWlLbDFVNG9rU1JPRlN2dlVSaFZaLWwxVlNKTlNKNkd6NlVMRU8xQi0xMWlpMGxPMkwyUE1DVnpFbHVoT205VExERWNuRTBLMmlIeXhlZmFDOVZDbFdzNGZXTExIblpkQlA4d1NHMlZfeXRQU09Zb3AtYjRiQmtVempXQ3pEb0trUjhRbmFYZUpjYWhvQ1Zrb3VfLUxHV2F6ZVVFMngtTHVMV3pMMFJ2WUx4T3JTMjdSRUNUaEc2YlZQcTNXbHQyakYxNFI3WEJBZ3RWSG1xR0RiaVl3d1VOampCRVlYV1JJWVBlQi04RlFsWF9NNjhQOUVHY0l6YU9fVzlPaUxYaTNwbTFOa3V3QkEwRHlEa18xSU1WSS1kMnRPTDNxY1Mtdl9kdlF3S3A0UUpMb09FTGQ4RDFheWZSUjVfXzNmUkNBUzdsdlhUOExMQWoxaDg2ZENKVU5nS0VrUmJkcU1qMGh4QllVVFFcIixcImVuY3J5cHRlZF9rZXlcIjpcIkFRSUJBSGc0MnEyZXBScGU0WklaZDU4dHVhQkVPcVYtME4temZpWmZhSTVRd1NEQm9BRktVSkFzVzFpeE5PdFJBMEFENzlJVEFBQUFmakI4QmdrcWhraUc5dzBCQndhZ2J6QnRBZ0VBTUdnR0NTcUdTSWIzRFFFSEFUQWVCZ2xnaGtnQlpRTUVBUzR3RVFRTXhlQzkxQUNwTXl3VTY0OUZBZ0VRZ0R2bzFVQjhqa1FyLVFHYV9sbG9EXzN1T2NaYWtjc21lQWl4RHhvSUVRbVJZM2pKbktLQmhXYjdYTnlYX0laalBnaXg3MEVLUF9VN0ZTbTVLQVwiLFwiaGVhZGVyXCI6e1wia2lkXCI6XCJhcm46YXdzOmttczp1cy1lYXN0LTE6ODk4MDg0OTg0ODc3OmtleS9tcmstYzc5YzRjZjZiOTcwNDY0MWFkOGQ5MmY2MjQ0YzgzNTBcIn0sXCJpdlwiOlwibVNybmlQZHJRYkhpakk3a1wiLFwicHJvdGVjdGVkXCI6XCJleUpoYkdjaU9pSkJWMU5mUlU1RFgxTkVTMTlCTWpVMklpd2laVzVqSWpvaVFUSTFOa2REVFNJc0lucHBjQ0k2SWtSRlJpSjlcIixcInRhZ1wiOlwiVlBmQW5wNWVXSWkzT3J3UVdhRkRrUVwifSIsImV4cCI6MTc1NzQyODc0NCwiaWF0IjoxNzU3NDI4MTQ0LCJpc3MiOiJodHRwczovL2lkZW50aXR5LmNpYW0ucmVmaW5pdGl2LmNvbS9hcGkvaWRlbnRpdHkvc3RzX3Byb2QiLCJyczEiOiI4NTdlZThlMDE4MTc2ZWYyMGJlZGUwNDQ5YjA1NTI3YTU4Nzg4M2NiIn0.cU88x7YT0hpLxXLJi0fqpE54LKi7Aui02cQKbGJoNo_u5M3Fr_55bAQn5YaDYn-9j6REKk3koAjib6ACdqZMiJJpYz78ISDR6DDfngd3i_4GgGwMPDAczXICihX8sYQdHz6mpTYsuJrITbdhWGWUwOXndUZNFaPVhW4XN4mmW0XjbjoY1xh9ZrQIplctB1DsoWLWLR9HQmfJCQQzAHN-Ad-KxK0DQM0z5tQsUHkV4hzp4LYUVn_sBHhXaCaFVW0zgc2UIjFrpu4XUNZN8dR5nX-1BpzeaFCnTNXtn1oz6xn7RziIG_0pDVo3QlWZPamcIVreiZ6F3loDd1RhvpLl9w", "refresh_token":"d0b87d02-f13f-4d97-9d49-71bae9ec5e6b", "expires_in":"600" , "scope":"trapi.streaming.pricing.read", "token_type":"Bearer" } 

Right after that, we can see a new HTTP request sent to following endpoint:

                https://api.refinitiv.com/streaming/pricing/v1?dataformat=rwf&transport=tcp

And as HTTP reponse, instead of Service Discovery JSON payload, we got 404.

                HTTP/1.1 404 Not Found

    Date: Tue, 09 Sep 2025 15:07:13 GMT

    Content-Type: text/plain

    Content-Length: 18

    Connection: keep-alive

    Access-Control-Allow-Headers: authorization,content-type,x-tr-correlationid

    Access-Control-Allow-Origin: *

    X-Amzn-Trace-Id: Root=1-68c042a1-53b867f827af08974a960f7b

    X-Content-Type-Options: nosniff

    X-Served-By: region=us-east-1; cid=ad4a7a621ae84425a23846b4ae13a123

    X-Tr-Requestid: fd4f8db5-8f5f-42a5-b21a-d1fe82bb0634

    Content string:

        404 page not found

 

Attaching the log as well.

refinitiv.log

Jirapongse

@AlissaCarla

Thank you for reaching out to us.

The ServiceDiscoveryURL is incorrect.

09 Sep 2025 11:03:26,409 INFO  [ConfigTemplStaticConfigProcessor] ConfigTemplStaticConfigProcessor: Configuration [JRefinitivAWSAgent]: load parametar ServiceDiscoveryURL=

https://api.refinitiv.com/streaming/pricing/v1

The correct URL is https://api.refinitiv.com/streaming/pricing/v1/, with a trailing slash at the end.