Failed to request authentication token information with HTTP error 500

thilinaillangasinghe

Hi, I received HTTP error 500 for following connect request (EMA, C++, Real-Time-SDK-2.0.1.G1 ). Any idea what could this be ? Note that i did not exceprience this issue in a different env (another redhat8) with same client application. I could've assumed this to be related with some env configs, but 113_MP_SessionMgmt example was executed successfully in the same environment in which following issue was noticed.

loggerMsg
    TimeStamp: 11:21:12.001
    ClientName: ChannelCallbackClient
    Severity: Verbose
    Text:    Attempt to connect using
        1] RSSL_CONN_TYPE_ENCRYPTED
        Channel name Channel_1
        Instance Name Consumer_1_10
        RsslReactor 0x0x7f944791ed50
        InterfaceName
        hostName
        port
        CompressionType None
        tcpNodelay false
        ObjectName
        ProxyHost
        ProxyPort
        SecurityProtocol 4
        EnableSessionManagement 1
        Location eu-west-1
        reconnectAttemptLimit 10
        reconnectMinDelay 1000 msec
        reconnectMaxDelay 5000 msec
        connectionPingTimeout 60000 msec
        initializationTimeout 10 sec

loggerMsgEnd

loggerMsg
    TimeStamp: 11:21:12.330
    ClientName: ChannelCallbackClient
    Severity: Error
    Text:    Failed to add RsslChannel(s) to RsslReactor. Channel name(s) Channel_1
        Instance Name Consumer_1_10
        RsslReactor 0x0x7f944791ed50
        RsslChannel 0
        Error Id -1
        Internal sysError 0
        Error Location /home/ec2-user/ema_tmp/Real-Time-SDK-master/Cpp-C/Eta/Impl/Reactor/rsslReactor.c:6876
        Error Text Failed to request authentication token information with HTTP error 500. Text: {"error":"500" ,"error_uri":"<>" ,"error_description":"Request b1714bed-a974-4385-8942-3717998621eb has fail
ed" }
loggerMsgEnd

wasin.w

Hello @thilinaillangasinghe

Firstly, you are using the RTSDK version 2.0.1.G1 which is the development release and is not recommended to run on the production environment. The information on the release types is as follows:

• "L" releases (e.g., 1.2.0.L1) are full RTSDK releases that have been fully tested and recommended for the production
• "E" releases (E-Loads) are emergency RTSDK releases for fixing specific issues
• "G" releases (e.g., 1.2.0.G1) are releases that are the development release.

I highly recommend you re-test the issue with the latest SDK version 2.0.5 L1. You can download the SDK from the following links:

• RTSDK download page on the Developer Community website: https://developers.refinitiv.com/en/api-catalog/refinitiv-real-time-opnsrc/rt-sdk-cc/downloads
• GitHub: https://github.com/Refinitiv/Real-Time-SDK/tree/Real-Time-SDK-2.0.5.L1
• GitHub: https://github.com/Refinitiv/Real-Time-SDK/releases/tag/Real-Time-SDK-2.0.5.L1

The error message indicates that the API got HTTP error 500 from the RDP Authentication service while it tried to send the authentication request to RDP. Can you test a connection from that machine to RDP Auth Service with the following command?

curl --location --request POST 'https://api.refinitiv.com/auth/oauth2/v1/token'; \
--header 'Content-Type: application/x-www-form-urlencoded' \
--header 'Authorization: Bearer ' \
--data-urlencode 'username=<Machine ID>' \
--data-urlencode 'password=<Password>' \
--data-urlencode 'grant_type=password' \
--data-urlencode 'scope=trapi' \
--data-urlencode 'takeExclusiveSignOnControl=true' \
--data-urlencode 'client_id=<App Key>'

If you can replicate the issue on demand, please enable the REST log messages and share the error messages (please remove your credentials) in this post. You can set the REST log with the following parameters on the EmaConfig.xml file.

Additionally, are you using the same RTO Machine-ID with multiple applications/sessions?