• State Not Answered
  • Replies 6 replies
  • Subscribers 5 subscribers
  • Views 2292 views
  • Users 0 members are here
Options
Related

The Bearer-Token is invalidated after 12 hours ( Trados Studio API + Groupshare TMs)

Hendrik Striepe

Dear RWS team, dear community,

we are developing an application which uses the Trados Studio 2019 / 2021 API with Groupshare 2017 / 2020 TMs. Unfortunately, the Studio 2019 ( 15.2.8.3007 ) API does not renew its authentication token if our application keeps running for more than 12 hours. The GS 2017 ( GS: 14.2.60175.10 - SR1 CU10 ) TMService.log explicitly states:

2021-04-30 15:25:44.9247|OURGSSERVER|Warn|THREAD_ID:32|TR_ID:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx|Authentication failed: The message expired at 29.04.2021 03:41:24 and it is now 30.04.2021 15:25:44.
2021-04-30 15:25:44.9247|OURGSSERVER|Warn|THREAD_ID:32|TR_ID:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx|Unauthorized request

We could reproduce the error message when creating a bearer token manually from GS 2017 using Postman with the following commands: groupshareserver/authentication/api/1.0/login with access to ["ManagementRestApi", "ProjectServerRestApi", "TMServerRestApi"] and afterwards groupshareserver/api/tmservice/tms for testing the validity of the token. If we tested the second call during the next day, the log states that the token is invalid after 12 hours, see error message above.

The error lies within the Studio API, since we only communicate with the GS through the project automation API, see issue: https://community.sdl.com/developers-more/developers/language-developers/f/sdk_qa/34244/unexpected-exception-when-initializing-task-using-server-tms-on-groupshare-2017-server-failed-to-initialize-translation-engine-follows which is exactly the way the error occurs in the first place.

  • Is there a possiblity to make the Studio API renew the token manually, like calling a non-editing endpoint?
  • Is there another way of accessing TMs within a project, that does not fail after 12 hours?
  • If not, is it possible to fix this issue of the Studio 2019 API?

Our assumption is that possibly not all objects are cleaned up correctly by the GC, since a restart of our application does reset the problem (until the next 12 hour timespan). On our side we end the API call with FileBasedProject.save(), dereferencing the object, and even a GC.collect() did not help. Somewhere in the API the bearer token still will be held.
Rate translation
×
Suggest better translation
×
Parents
  • 0

    This will need to be escalated to the Studio Team; I will follow up...

    It seems like the procedure to re-login automatically after the token has expired is not executed while accessing a server resource via the Project Automation API.  I can only assume that it was not anticipated that an automation procedure would exceed 12 hours.

    A practical workaround would be to simply restart the automation procedure that your team are running through the Project Automation API, either at set intervals and/or when this particular exception is invoked.

    -- Dev Notes

    A solution was implemented with the latest CU for 2019 (build 15.2.8.3007) to resolve the failing connection with GS.  The team have reported that this is not working, against build 15.2.8.3007

    Cumulative Update 8 for SDL Trados Studio 2019 SR2 (Build 15.2.8.3007, Released on 26 January 2021)
    https://gateway.sdl.com/apex/communityknowledge?articleName=CUs-Studio2019SR2

    • Trados Studio no longer loses connection to server-based translation memories (TMs) after 12 hours of editor inactivity. Instead, the GroupShare token is now automatically renewed for Windows and SDL authentication. For SSO authentication, you are prompted to log back in, without having to reconnect again to the GroupShare server. (CRQ-10873, LG-26638).
Reply
  • 0

    This will need to be escalated to the Studio Team; I will follow up...

    It seems like the procedure to re-login automatically after the token has expired is not executed while accessing a server resource via the Project Automation API.  I can only assume that it was not anticipated that an automation procedure would exceed 12 hours.

    A practical workaround would be to simply restart the automation procedure that your team are running through the Project Automation API, either at set intervals and/or when this particular exception is invoked.

    -- Dev Notes

    A solution was implemented with the latest CU for 2019 (build 15.2.8.3007) to resolve the failing connection with GS.  The team have reported that this is not working, against build 15.2.8.3007

    Cumulative Update 8 for SDL Trados Studio 2019 SR2 (Build 15.2.8.3007, Released on 26 January 2021)
    https://gateway.sdl.com/apex/communityknowledge?articleName=CUs-Studio2019SR2

    • Trados Studio no longer loses connection to server-based translation memories (TMs) after 12 hours of editor inactivity. Instead, the GroupShare token is now automatically renewed for Windows and SDL authentication. For SSO authentication, you are prompted to log back in, without having to reconnect again to the GroupShare server. (CRQ-10873, LG-26638).
Children
No Data