Missing AuthenticationTTReissue field in Login response with Authentication V2

Hello,
We're using the Real-Time Optimized API via websockets. The login response elements container previously contained an 'AuthenticationTTReissue' value when using V1 authentication. This appears to be missing when using the new V2 authentication. I also don't see this value in the current API specification; can someone confirm that we will no longer receive a AuthenticationTTReissue value in the login response?

Thanks!
Will

Tagged:

Best Answer

  • Gurpreet
    Answer ✓

    Hi @wzimmerman,

    The authentication mechanism and the way token used to expire has changed in v2 authentication. This field is still sent out in V1 response, but not in the v2 response because as long as your application is connected to the v2 auth session, the token does not need to be reissued.

Answers

  • Hello @wzimmerman

    Like my colleague has mention, the application/API does not need to renew an Access Token (HTTP/RSSL-WebSocket) as long as the streaming channel (WebSocket/RSSL) is active with the Version 2 authentication.

    The Version 2 authentication request-response messages HTTP structures are as follows:

    Request:

    POST /auth/oauth2/v2/token HTTP/1.1
    Accept: */*
    Content-Type: application/x-www-form-urlencoded
    Host: api.refinitiv.com:443
    Content-Length: XXX


    client_id=KKKKKKKKKKKKKKKKKK
    &client_secret=BBBBBBBBBBBBBBBBBBBB
    &grant_type=client_credentials

    Response:

    {
      "expires_in": 7199,
      "token_type": "Bearer",
      "access_token": "YYYYYYYYYYYYY"
    }

    where:

    • access_token: The token used to invoke REST data API calls as described above. The application must keep this credential for further RDP APIs requests.
    • expires_in: Access token validity time in seconds.
    • token_type (required): The type of token this is, typically just the string “Bearer”.

    You can find more detail about the Version 2 authentication on the following articles: