While performing a Check Out, Lock, Check In or Unlock operation using the desktop client GUI, the following warning message is shown: ttsourcebridge.dll is not compatible to work with SSO token This only happens for files in Project Databases that are configured to use the SSO (Serena Single Sign-On) login source.
In certain SBM Configurations involving https Load Balancer URLs it can lead to users not being able to log in and receiving "Error decoding base64 encoded token in HTTP header "ALFSSOAuthNToken" errors in the sso -gatekeeper log.
The above error can occur if the various servers times are out of sync as much as 5 minutes or more. Verify that the SBM SSO Server and Dimensions CM Server have the same time between them.
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163) at org.eclipse.alf.security. sso .common.ws.client.RSTCallProxy.internalGenericInvoke(RSTCallProxy.java:480) at org.eclipse.alf.security.sso.common.ws.client.RSTCallProxy.internalRSTInvoke(RSTCallProxy.java:409)
If during the creation of a snapshot, AR via the SLA XML file creation process is unable to validate the user / acquire an SSO token , the SLA XML file will be populated with the follow JSON. The snapshot does get created, but the SLA XML is corrupt / not an XML file.
ALF SSO Gatekeeper error has occured: Error obtaining security token . ... Validation of occurred-Federation token failed with code 40: Token issuer not allowed. This message indicates that you may need to update the SSO STS certificate from SBM into the Dimension RM side.
When multiple servers are sharing the same Repository, the SSO certificates must match across all servers. If these certificates do not match, you may see the following error when logging into the Repository or during deploy:
