Login/Register
  • Home
  • Community
  • Knowledge
  • Technical Docs
  • RWS Support Policy
  • Trados Studio Licensing Help
  • Login for Support
Back to Search Results

Trados Studio SSO users are disconnected from Trados GroupShare - Invalid URI: The format of the URI could not be determined

000019576 |3/14/2023 10:10 AM
Scope/Environment
Trados GroupShare 2020 SR1 CU7
Trados Studio 2021
Trados Studio 2022
Symptoms/Context
Users logged in to Trados GroupShare 2020 SR1 CU7 with Single Sign-On are encountering an error when performing actions that require a connection to Trados GroupShare, typically occurring after around 1 hour after the initial connection was established:

Invalid URI: The format of the URI could not be determined

Invalid URI: The format of the URI could not be determined

In some instances, the error is not showing up in the Trados Studio User Interface but users are blocked from performing actions in Trados GroupShare.
Under File > View Log File, the following error is logged:
 
Sdl.ProjectApi.Implementation.Server.CommuteServerSyncDaemon - Failed to synchronize project
System.UriFormatException: Invalid URI: The format of the URI could not be determined.

Server stack trace: 
   at System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)
   at System.Uri..ctor(String uriString)
   at Sdl.Desktop.Platform.ServerConnectionPlugin.Client.Communication.ServerApi.<SamlTokenFromBearerAsync>d__11.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Sdl.Desktop.Platform.ServerConnectionPlugin.Client.Communication.ServerApi.SamlTokenFromBearer(String bearer)
   at Sdl.Desktop.Platform.ServerConnectionPlugin.Client.IdentityModel.IdentityInfo.IssueTokenFromRest(WCFToken wcfToken)
   at Sdl.Desktop.Platform.ServerConnectionPlugin.Client.IdentityModel.IdentityInfo.GetSecurityToken()
   at Sdl.Desktop.Platform.ServerConnectionPlugin.Client.IdentityModel.IssuedTokenMessageHeader..ctor(IdentityInfo idInfo)
   at Sdl.Desktop.Platform.ServerConnectionPlugin.Client.IdentityModel.IssuedTokenMessageInspector.BeforeSendRequest(Message& request, IClientChannel channel)
   at System.ServiceModel.Dispatcher.ImmutableClientRuntime.BeforeSendRequest(ProxyRpc& rpc)
   at System.ServiceModel.Channels.ServiceChannel.PrepareCall(ProxyOperationRuntime operation, Boolean oneway, ProxyRpc& rpc)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

 
Resolution

Server-side Workaround:

1. On the Trados GroupShare Web Server, use Notepad++ to open AuthnRedirect.cshtml, which by default is located at: C:\Program Files (x86)\SDL\SDL Server\Web\TokenExchange\Views\AuthnResponse\
Comment line 13 which says:
document.cookie = 'sso_saml_token=@Html.Raw(@Model.SamlToken);path=/';
The commented line should look like below:
<!-- document.cookie = 'sso_saml_token=@Html.Raw(@Model.SamlToken);path=/'; -->

2. Restart IIS.
3. Once the server-side actions were performed, the users need to restart their Trados Studio clients.

Studio Workaround:

Go through File > Setup > Servers, double-click your server connection and go through the login wizard. This needs to be repeated every hour or whenever the issues are encountered so the server workaround is recommended.
 
Root Cause
This is a defect reported to our Development Team under CRQ-31278.
 
Reference
Send Article Feedback
RWS Machine Translation Translation Software Language Services Content Management
All Contents Copyright © RWS.
COPYRIGHT PRIVACY POLICY COOKIE POLICY TERMS AND CONDITIONS