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 Dim12: SSO: When using a Load Balancer with Dimensions CM and SSO, the Dimensions CM Servers provide error messages
When using a Load Balancer with Dimensions CM and SSO where the SSO Server resides on the SBM Server, the Dimensions CM Servers provide error messages similar to the following: ALF SSO Gatekeeper error has occurred: Error processing federation services response. Detail
CMS-XML Clustering JBoss with SSO Enabled and Securing Your Load Balancer
3) In the gatekeeper-core-config.xml file, ensure that the @external STS endpoint is configured for HTTPS as follows (replace admin.serena.com with the hostname of your load balancer machine): End point reference for Security Token Service (STS) endpoint.
CMS-XML 404 error when trying to load SSO login page - server.log has error regarding "sbmSAML2SPConfigFilter"
404 error when trying to load SSO login page - server.log has error regarding "sbmSAML2SPConfigFilter"
CMS-XML ALF SSO library: 'Error while creating JVM: 'Unknown error occurred while loading JVM
After setting up Serena Single-SignOn to work with various Serena products, the following message may occur when logging into SBM. ALF SSO library: 'Error while creating JVM: 'Unknown error occurred while loading JVM If this error occurs check the sso-gatekeeper.log,
CMS-XML 404 error when trying to load Application Repository, user workspace, or Work Center when SSO is enabled
The SSO login can return a 404 error if SSO fails to start correctly when SBM Tomcat is started. One possible indication of this issue is an error similar in the SBM Configurator log:
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 Orchestration Engine renew errors when using SQL Server with Windows Authentication - Can't create connection to the database ... I/O Error: SSO Failed: Native SSPI library not loaded. Check the java.library.path system property
Orchestration Engine renew errors when using SQL Server with Windows Authentication - Can't create connection to the database ... I/O Error: SSO Failed: Native SSPI library not loaded . Check the java.library.path system property
CMS-XML Error when starting the Application Engine: Unable to initialize ALF SSO library: 'Error while creating JVM: 'Not enough memory to load JVM''
Error (1) occurs because there is not enough memory left in the OS to load the JVM. Error (2) has also been known to sometimes occur for the same reason.
CMS-XML One or more VM I-Net Web Client users find that module assocations made via SourceBridge do not get stored if VM and SBM are both using SSO authentication
In a setup where SBM and VM are both configured to use SSO authentication , some users may find that SBM issues they associate during checkin do not get stored, despite those users being able to select and assocate issues in the SourceBridge Web Client dialog.
CMS-XML Issues with Dimensions Desktop client and ActivIdentity / ActivClient SSO / CAC client.
Dimensions CM Desktop Client will look for, and try to load ActivIdentity / ActivClient DLLs. Occasionally this may result in errors in login dialog, or login dialog hanging, or not opening at all.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs