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 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 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 ALF SSO library: 'Error while creating JVM: 'Unknown error occurred while loading JVM
If this error occurs check the sso-gatekeeper.log, as well as, the sso-sts.log and/or the sso - idp.log
CMS-XML LDAP and SSO: When the SearchBase of an LDAP look up of Active Directory Server is set to the root of the tree, it is possible to get PartialResultException - Error processing LDAP search result(s): null
When the SearchBase of an LDAP look up of Active Directory Server is set to the root of the tree for LDAP and SSO then authentication does not work. If you have "referrals" selected then you get the following error in sso - idp.log : Example error:
CMS-XML SmartCard (CAC) authentication from VM desktop clients to an SBM SSO server breaks after upgrading to SBM 11.4
This error corresponds with the following entry getting added to SBM's sso - idp.log file:
CMS-XML SSO with Windows Authentication checks for the existence of loginid with the domain stripped it
SSO - IDP.LOG returns "org.eclipse.higgins.idas.api.IdASException:" in web services. Work Around
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs