RTO service discovery TLS certificate mismatch when using api.refinitiv.com – inconsistent behavior

Souradeep

Hello,

We are encountering the below exception when trying to connect to the RTO endpoint for service discovery:
Failed to query RDP service discovery for Refinitiv Rto. Error text: failed to submit authorization request, exception = Certificate for <api.refinitiv.com> doesn't match any of the subject alternative names: [eu-west-1-aws-1-sm.optimized-pricing-api.refinitiv.com, eu-west-1-aws-1-sm.optimized-pricing-api.refinitiv.biz, eu-west-1-aws-1-sm.optimized-pricing-api.refinitiv.net, eu-west-1-aws-2-sm.optimized-pricing-api.refinitiv.biz, eu-west-1-aws-2-sm.optimized-pricing-api.refinitiv.com, eu-west-1-aws-2-sm.optimized-pricing-api.refinitiv.net, eu-west-1-aws-3-sm.optimized-pricing-api.refinitiv.biz, eu-west-1-aws-3-sm.optimized-pricing-api.refinitiv.com, eu-west-1-aws-3-sm.optimized-pricing-api.refinitiv.net]

The configuration that we are using is as below:

REFINITIVRTO_AUTHENTICATION_URL  = https://api.refinitiv.com/auth/oauth2/v2/token
REFINITIVRTO_SERVICE_DISCOVERY_URL  = https://api.refinitiv.com/streaming/pricing/v1/service-discovery
REFINITIVRTO_SERVICE_DISCOVERY_LOCATION  = eu-west-1

One important thiong to note is that this exact same configuration works fine in one of our environments, but throwing the above exception in another.

wasin.w V3

Hello @Souradeep

According to my research, the "Error text: failed to submit authorization request, exception = Certificate for <api.refinitiv.com> doesn't match any of the subject alternative names: [RTO endpoints" error message is most likely to be a network issue from the following factors:

• Corporate firewall or proxy interception the HTTPS request that causes the certification issue. You might need to contact your Network team.
• DNS resolution issue for the api.refinitiv.com. Please see the api.refinitiv.com static IP document if you need to whitelist the api.refinitiv.com IP Address.
• Wrong endpoint configuration.

Can you try this curl command in the environment that encounters the issue?

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'

Please be informed that the endpoint for the RTO Service Discovery is /streaming/pricing/v1/ url, not the /streaming/pricing/v1/service-discovery url. It does not contain /service-discovery path.

You can check on the RDP API Playground page and Real-Time - Optimized Install and Config Guide document.

Please try to set the REFINITIVRTO_SERVICE_DISCOVERY_URL to https://api.refinitiv.com/streaming/pricing/v1/ value like this RTO Example and see if the problem still persists.