Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML ALF SSO Gatekeeper error has occurred: Error obtaining security token. Validation of WS-Federation token failed with code 40:Token issuer not allowed.
ALF SSO Gatekeeper error has occurred: Error obtaining security token . Validation of WS-Federation token failed with code 40:Token issuer not allowed.
CMS-XML VM desktop client GUI shows error "ttsourcebridge.dll is not compatible to work with SSO token"
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.
CMS-XML Impossible to authenticate, sso-gatekeeper gives - Error decoding base64 encoded token
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.
CMS-XML Dim12: SSO: SSO Gatekeeper error has occurred:Error obtaining security token. Detail -Validation of WS-Federation token failed with code 10:Token is expired
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.
CMS-XML CM/SDA/SRA/SDA/RLM: Error "SSO Gatekeeper error has occurred: Error obtaining security token. Validation of WS-Federation token failed with code 40:Token issuer not allowed"
To update your SSO STS certificates: On the server where SBM is installed: If you are using SBM 10.1.1.4+:
CMS-XML VM: How to import an updated SSO STS Trust Certificate / How to solve "Invalid SSO token" errors
utility that was created to easily copy SSO certificates. See KB doc
CMS-XML Authentication error: SSO token is empty
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)
CMS-XML AR: Incorrect behavior in case - not valid SSO token when creation snapshot
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.
CMS-XML DIM RM: ALF SSO Gatekeeper error has occured: Error obtaining security token.
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.
CMS-XML SBM: Error "SSO Gatekeeper error has occurred: Error obtaining security token" during login to Repository or deploy
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:
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs