Recived token not working

miguel.alvarez

Hello,

We are having a problem with the connection token.

Some times, when we get the token from refinitiv we get rejected:

Getting the token:

{
  "Domain":"Login",
  "ID":1,
  "Key":{
    "Elements":{
      "ApplicationId":"739590397752477c9d02dde57af75cf77f98b680",
      "AuthenticationToken":"eyJ0eXAiO...

Error:

[
  {
    "Domain":"Login",
    "ID":1,
    "Key":{
      "Name":"AQIC5wM2..."
    },
    "State":{
      "Code":"Error",
      "Data":"Suspect",
      "Stream":"Closed",
      "Text":"Login Denied:Failed to lookup sso token - AQIC5wM2..."
    },
    "Type":"Status"
  }
]

[
  {
    "Domain":"Login",
    "ID":1,
    "Key":{
      "Name":"AQIC5wM2LY4SfcwgOg%2BShT6xwuDp%2F3uHT7p%2FVYezE8RTGHQ%3D%40AAJTSQACMTAAAlNLABQtMjIzNDM1ODM4NjMzOTgwMTMyNQACUzEAAjI4%23"
    },
    "State":{
      "Code":"Error",
      "Data":"Suspect",
      "Stream":"Closed",
      "Text":"Login Denied:Failed to validate sso token"
    },
    "Type":"Status"
  }
]

If we reset the connection, it works fine.

This is happening randomly, most of the times do not happen actually.

Any ideas why this is happening?

Thank you,

Gurpreet

Hi @miguel.alvarez,

Has the application been working in the past or is this a persistent issue? Are you using one of the samples for this websocket application; if so which one? Usually, sso errors occour during an outage at Refinitiv, so far I don't see any service alert for it - https://insightalerting.refinitiv.com/a/alerts/servicealerts/Alert/Alerts.aspx

On the side note, I notice that you have a long string in the Application ID. Historically, this is a number between 1 - 255, so can you please shorten it and try again.

wasin.w

Hello @miguel.alvarez

This "Login Denied:Failed to validate sso token" authentication error message is generated from the RTO WebSocket server.

Does the application always receive a new access token from the RDP Auth service (https://api.refinitiv.com/auth/oauth2/v1/token) and send it to the WebSocket via a JSON login message? If so, please try to shorten the application id as suggested by my colleague.

If the problem still persists, please contact the RTO directly to help you verify the issue on the server-side. You can submit a ticket to the RTO support team via the my.refinitiv.com website.