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 VM: SSO Login fails with error "Failed to verify signature"
An attempt to login to Version Manager that is configured to use an SSO server fails . The login page shows the error Failed to verify signature
CMS-XML 10.1-10.1.1.3 (Earlier versions affected if SSO On) - SBM Sample Certificates for STS, Federation Server and SSO Gatekeeper expire on 13th June 2015 or 16th September 2017 - Error message: Failed to verify signature
10.1-10.1.1.3 (Earlier versions affected if SSO On) - SBM Sample Certificates for STS, Federation Server and SSO Gatekeeper expire on 13th June 2015 or 16th September 2017 - Error message: Failed to verify signature
CMS-XML HSSO - Hybrid SSO for SaaS environments- cannot logon as getting Untrusted Endorsing Credentials or Failed to verify signature - certificates expired and need updating
There are some certificates built into HSSO and On-Demand. If these expire then the end user will get the error "Failed to verify signature". The HSSO log will contain the error "The signature or decryption was invalid (the provided certificate is invalid)”.
CMS-XML Dim CM: Getting error "certificate verify failed; self signed certificate in certificate chain" in SDP trace output attempting to use ALF events with SBM
Open https://<server>:8443 in a browser, check what certificate is used and export it to a file. - if it is self- signed certificate, export certificate itself - if not self-signed then export all CAs chain
CMS-XML Unable to validate user, please contact your Administrator.Failed to verify signature: The message has expired
2015-08-25 09:41:29,571 ERROR TS 10.100.10.62 f: g: EndorsingCredentialsHandler.processMessageSignature(603): Failed to verify signature : The message has expired (WSSecurityEngine: Invalid timestamp The security semantics of the message have expired) org.apache.ws.security.WSSecurityException: The message has expired (WSSecurityEngine: Invalid timestamp The security semantics of the message have expired)
CMS-XML After upgrading to VM 8.6.1 or newer, HTTPS connections to the File Server may fail with SSL routines:ssl3_get_server_certificate:certificate verify failed
Have a Common Name (CN) or alternate DNS name matching the URL being used to access the server Be signed by a Certificate Authority (CA) known to the Java Runtime Engine (JRE) contained within VM (e.g VeriSign, DigiCert, GeoTrust, thawte, etc.) Not be expired
CMS-XML SLM 2.3.0 mlclient fails to check named licenses out if the first key in the license file for that feature is invalid
If the serena.lic file has multiple named license keys for a feature, and the first of those keys is invalid (for example due to a bad signature , mismatched HOSTID, expired temporary license, etc.), then the valid keys will get skipped and none of the named licenses for that feature can be checked out , (typically) showing the error:
CMS-XML Certificate signature failure
"LDAP bind authentication failure with Search Authority-Bind: 81 Can't contact LDAP server" Please check the event viewer for the detailed message on this error. You need to double check your certificate if you see this "Information" from Event Viewer:
CMS-XML Failed to create the item in the Design part when its name includes a at sign or comma
<p> So either Document needs update and we denial users to use those characters or we make sure the command escapes the character correctly </p>
CMS-XML SBM: Error "Failed to obtain security token" and "soap_wsse_verify_X509" when deploying to some environments
When SBM components are installed across multiple servers, each server must have matching signed certificate trust keys. This allows the servers to communicate with each other. If the certificates don't match, you could see any number of problems.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs