Find Answers

Filter Search Results
All Operating Systems:
All Others (6)
All Unix (61)
All Windows (206)
All Products:
ChangeMan ZMF (1)
Development Manager (5)
Dimensions CM (107)
Dimensions RM (17)
PVCS Version Manager (41)
Project Portfolio Management (1)
Release Manager (21)
SBM (218)
Service Manager (27)
Agile (1)
Agile Planner (1)
Application Development Management (1)
Application Release Manager (1)
Builder (1)
Collage (4)
Deployment Automation (14)
Licensing (3)
Portfolio Edge (1)
Project Office (3)
Release Automation (11)

More...
All Solution Types:
Documentation Update (83)
Error Message (128)
Installation & Customization (144)
Product Tips & Advice (175)
Source:
Solutions (392)
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML How to change logging level in the SSO-Idp.log file
How to change logging level in the SSO - Idp.log file
CMS-XML "Premature end of file" error in sso-idp.log or mashupmgr.log
"Premature end of file" error in sso - idp.log or mashupmgr.log
CMS-XML Certificate validation failed: Path does not chain with any of the trust anchors in sso-idp.log file.
Certificate validation failed: Path does not chain with any of the trust anchors in sso - idp.log file.
CMS-XML What does the following error mean in the sso-idp.log? "SSOHelper.getLocale(823): Invalid locale string: null"
What does the following error mean in the sso - idp.log ? "SSOHelper.getLocale(823): Invalid locale string: null"
CMS-XML Unexpected error while resolving identity: null on login screen and also in sso-idp.log
The following error will happen as a result of the SSO keystore files having a blank password. You will see the following error in sso-idp.log and you will also see the following on the login screen after attempting to login.
CMS-XML DimCM: SSO: LDAPS: Cannot initialize LDAP Context
Error from the sso - idp.log file:
CMS-XML VM: SSO Login fails with error "Failed to verify signature"
Examining the file sso - idp.log
CMS-XML See repeated errors in sso-idp.log about the following "Trusted certificate expired and will be discarded: CN=Serena Version Manager Server..."
The SSO certificate used for integrations with SBM and Version Manager expired on June 15, 2015 for some older versions of SBM. Since that date you may see errors like the following in the sso-idp.log file that happen quite frequently.
CMS-XML DimCM: When logging out of Web Client or AdminConsole, a Logout failed (USERNAME) occurs when using SBM SSO
The SBM sso - idp.log file shows the following:
CMS-XML DimCM: SSO Server: Enabling additional logging for the Dimensions CM SSO Server
This tracing will increase the logging within the $Tomcat\logs\ sso - idp.log file.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs