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 "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 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 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.
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 DimCM: SSO Server: Desktop Client will provide an error of PRG7700105E Error: Multiple users have been found in LDAP
User authentication failed The sso - idp.log file shows: 2019-10-18 16:09:43,661 TRACE TS 10.110.200.59 f: g: LDAPAuthenticator.internalAuthenticate(215): Authenticating user "username1"
CMS-XML "PRG7700105E Error: Error authenticating user (-1,073,741,715): Logon Failure" when using SSO to connect to Dimensions Desktop Client
DMPOOL 2015/01/16 12:34:53 E P60308 T59876 Authentication failed for user xxxxxxxx - 3 () When looking at the SBM SSO logs (by default, located at C:\Program Files\Serena\SBM\Common\jboss405\server\default\log\ sso - idp.log ), you will see these errors: IssueRequestProcessor.process(426): Error invoking WS-Trust request: Authentication failed
CMS-XML How to add identity transformer code to configuration.xml for CAC and PIV authentication.
TIP: In order to get debug logging to show in the sso - idp.log file you can change the "log.trace" lines to "log.info" below.
MS-WORD Dim 14.2 with SBM SSO Checklist.docx
$Tomcat\logs\ $JBOSS\default\log\ sso - idp.log $JBOSS\default\sso-gatekeeper.log
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs