Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML Dim2009R2: SSO CAC: PKIX path building failed: unable to find valid certification path to requested target.
The following error occurs when attempting to login after installing SSO/CAC: Error occurred
CMS-XML AR: Incorrect behavior in case - not valid SSO token when creation snapshot
{"status":" ERROR ","results":" Valid Serena Security Token Required for this operation."} The attached snapshot shows the issue in the RIS-sla.xml.
CMS-XML SSO server throws error: A request failed with the exception [com.ctc.wstx.exc.WstxLazyException] Unexpected character '(' (code 40) (expected a name start character)
This is typically caused by an LDAP search filter definition in the file VM_Install_Dir /vm/common/tomcat/ idp /WEB-INF/conf/Configuration.xml , like:
CMS-XML "Premature end of file" error in sso-idp.log or mashupmgr.log
"You must use a POST request to get answer from gsoap !" In this instance the error shown was the following: "HTTP Error 403" You Don't have authorization to view this page.
CMS-XML Dim2009R2: SSO CAC: Error acquiring remote data: SSL handshake failed PKIX path building failed: unable to find valid certification path to requested target
CMS-XML Error requesting security token - Read timed out - End Users experience very slow or non-responsive
AE Event Viewer SSO timeouts: Error occurred in file: 'AppDB_JavaBridge.cpp', line 735.
CMS-XML "Request is expired." received when attempting to login via SSO
This error will occur in a distributed install where the system clocks are out of sync by the default of 60 minutes or more. Make sure that all server components using SSO have their system clocks synchronized.
CMS-XML Dim12: SSO: When using a Load Balancer with Dimensions CM and SSO, the Dimensions CM Servers provide error messages
Detail Unsolicited or expired request OR
CMS-XML RLM gives error "No match with the browser requests service URIs: http://server:8080/serena_ra/." when trying to open the login screen
Also, in the sso -gatekeeper.log file (by default, located in C:\Program Files\Common\tomcat\6.0\logs) will show these errors:
CMS-XML SBM 11.4: Intermittent Error: "Invalid request challenge/response data on the request" after login
The authentication settings are as follows. * Browser sessions: " Single Sign-On " * Browser authentication: "SBM Login Form"
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Title: Dimensions CM: Deploying Emergency Fixes (demonstration)
This demonstration shows you how to deploy an emergency fix to a live production environment in Dimensions CM. You will learn how to promote requests to any stage in the Global Stage Lifecycle, promote and deploy in the same operation, and browse deployment areas.
Title: Dimensions CM: Scheduling Deployment (demonstration)
This demonstration shows you how to schedule a deployment in Dimensions CM. You will learn how to set a deployment sequence, schedule a deployment, and use the Queue tab in the Deployment view

Additional Assistance

  • Submit a Case Online
  • FAQs