Invalid Application Credentials with Websockets

Using websocket_authentication_argp.py and the credentials provided by the refinitiv team, I tried to connect to UAT and got "Invalid Application Credential".

Have the credentials somehow expired, or did I misunderstand the usage of the credentials?

More details, obtained by running with --debug 7:

Sending authentication request with password to https://api.ppe.refinitiv.com/auth/oauth2/v1/token ...
('https://api.ppe.refinitiv.com/auth/oauth2/v1/token',
{'headers': {'Accept': 'application/json',
'content-type': 'application/x-www-form-urlencoded'}},
{'data': 'grant_type=password&username=GE-A-<censored>&password=<censored>&client_id=GE-A-<censored>&takeExclusiveSignOnControl=true'},
{'auth': ('GE-A-<censored>', '<censored>')},
{'verify': True},
{'allow_redirects': False})
https://api.ppe.refinitiv.com/auth/oauth2/v1/token
grant_type=password&username=GE-A-<censored>&password=<censored>&client_id=GE-A-<censored>&takeExclusiveSignOnControl=true
{'User-Agent': 'python-requests/2.18.4', 'Accept-Encoding': 'gzip, deflate', 'Accept': 'application/json', 'Connection': 'keep-alive', 'content-type': 'application/x-www-form-urlencoded', 'Content-Length': '152', 'Authorization': 'Basic <censored>'}
RDP-API Gateway authentication HTTP code: 401 Unauthorized
response : {
"error":"invalid_client",
"error_description":"Invalid Application Credential."
}

Find more posts tagged with

websockets

Accepted answers

Gurpreet

Hi @m.rodriguesdossantos,

You are connecting to ppe endpoint and not the production one at https://api.refinitiv.com:443/auth/oauth2/v1/token. Can you please confirm that you can connect to it and that your credentials are valid on production setup as well.

All comments

Gurpreet

Hi @m.rodriguesdossantos,

Gurpreet

Better still, I would advise you ro try out the latest Service Discovery python sample provided.

m.rodriguesdossantos

Hey @Gurpreet ,

I don't want to connect to production yet as I'm in the early stages of development. I want to connect to UAT. Is this not the right endpoint?

Gurpreet

The main production endpoints can be used for development as well. I would advise you to try this and reach out to your account manager if it still doesn't work.

Also, use the Service Discovery example listed in other response.

m.rodriguesdossantos

Thanks @Gurpreet , using the production endpoint works.

I'll look into service discovery.

m.rodriguesdossantos

Next, the Login message doesn't work:

Connecting to WebSocket wss://contrib-ws1-emea1.uat.platform.refinitiv.com:443/WebSocket ...
WebSocket successfully connected!
SENT:
{
  "Domain":"Login",
  "ID":1,
  "Key":{
    "Elements":{
      "ApplicationId":"256",
      "AuthenticationToken":"<Censored>",
      "Position":"127.0.1.1/<machine-name>"
    },
    "NameType":"AuthnToken"
  }
RECEIVED:
[
  {
    "Domain":"Login",
    "ID":1,
    "Private":true,
    "State":{
      "Code":"NotEntitled",
      "Data":"Suspect",
      "Stream":"Closed",
      "Text":"Authentication unsuccessful"
    },
    "Type":"Status"
  }
]

Still using the code from the example mentioned above.

Is this not the right server to reach UAT?

umer.nalla

Hi @m.rodriguesdossantos

I have been advised that there is no UAT MachineID associated with your account.

contrib-ws1-emea1.uat.platform.refinitiv.com is a UAT endpoint

If you want to contribute to UAT - you will need to ask your Refinitiv account team to provide you with a MachineID which has been configured for UAT access.

Just to be clear, there is a UAT authentication endpoint and UAT Contribution endpoints - based on my understanding of your most recent posts, you are: