• State Suggested Answer
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 56 subscribers
  • Views 2024 views
  • Users 0 members are here
Options

Trados Team API - Authentication failed

Andreas Galambos

Greetings!

We are trying to use the API to get project information from Trados Team via Get Project. For that purpose, we created a Service User in Team, assigned Project Manager role, then used the "Integrations" feature to create an access token.

I then downloaded the Postman collection and made these settings:

Screenshot of an API request in Postman with the GET method selected and a blurred URL. The Authorization tab is open showing Bearer Token selected with a warning about sensitive data in variables.

As tenant ID, I used the 24 character ID following "languagecloud.sdl.com/lc/t/" in the dashboard URL:

Screenshot of Postman showing the Headers tab for a GET request with three headers: X-LC-Tenant, Accept, and lc_access_token, all with blurred values.

As you can see, I get "Authentication failed" without further details. As I understand the documentation, the parameter "client ID" and "client secret" are only required to generate an access token. Since this has already been generated in the Team UI, I should not require these, correct?

What am I missing here?

Thanks!

Best regards,

Andreas

Generated Image Alt-Text
[edited by: RWS Community AI at 8:15 AM (GMT 1) on 1 Oct 2024]
Rate translation
×
Suggest better translation
×
Parents Reply Children
  • 0 in reply to Anca Iuga

    Hi Anca,

    Sorry, I posted this response under the wrong comment: Thank you for that hint!

    I did set the Bearer token in Postman's Authorization section, so probably the lc_access_token part in the header is superfluous.
    I think the issue might be, that we had not created a custom application in Team to associate with the Service User. I will notify the customer's admin and post back if this changes anything.
  • 0 in reply to Anca Iuga

    Update: it works now! Thanks for putting me on track, Anca!

    Detail: the "access token" one gets through the UI does... nothing... What is required instead? A custom application and from it: client ID and client secret.
    Use it in the "Authentication" POST call. There you will receive the *real* bearer token which is very different from the access token. With this freshly received bearer token, the get project call works.

    So what is the access token from the UI integrations page for? As far as I can tell: absolutely nothing. ¯\_(ツ)_/¯

    Best regards,
    Andreas