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 Sample certificates in SBM expire on 16th September 2017 for SBM versions 10.1.x - you must update to avoid System Failure
Sample certificates in SBM expire on 16th September 2017 for SBM versions 10.1.x - you must update to avoid System Failure
CMS-XML VM 8.4.6: Combo HotFix 1 (Includes updated Certificate for VM I-Net Web Client Applet)
VM 8.4.6: Combo HotFix 1 (Includes updated Certificate for VM I-Net Web Client Applet)
CMS-XML How to create and update the SSO STS certificate in Dimensions CM
Serena recommends that you generate new key pairs to secure your SBM installation. If you do not generate new key pairs, then the default certificates that the STS inherently trusts are used. These same certificates are available from any SBM installation and can be easily spoofed!
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 Java Applet gives certificate revocation warning or fails to run after installing Java 7 Update 25 (or newer) on clients in a secured network
When Java 7 Update 25 (or newer) is installed on an end-user's PC in a secured network, meaning a network that cannot reach the Internet, attempts to run the web client for Dimensions CM or PVCS Version Manager may result in an warning similar to: If the Java Security Level has been set to Very High, instead of the message above users may get an error similar to: with the More Information button revealing:
CMS-XML 403.16 when trying to login after updating the client certificate in SBM
If you reimport the client certificate key and start getting a 403.16 error, you may be running into this problem. This may be a problem after upgrading to SBM 11.6+ from 11.3.1.
CMS-XML ZMF4ECL 7.1.2.01 Update Site needs a certificate to allow automated installs.
When attempting to perform an automated ZMF4ECL plug-in install using the new Update Site install process, the script fails and issues the following error message in the .LOG: !ENTRY org.eclipse.equinox.p2.engine 8 0 2012-06-11 15:25:17.586
CMS-XML Utility to update the SSO (Serena Single Sign-On) certificates used by PVCS Version Manager
Check if the selected Login Source is SSO/CAC A number of default SSO certificates used by Version Manager are set to expire: vmserver
CMS-XML VM: How to import an updated SSO STS Trust Certificate / How to solve "Invalid SSO token" errors
utility that was created to easily copy SSO certificates . See KB doc
CMS-XML Credential Set UCS Not Updating Properly
The command UCS to update a changed password is not working correctly. When a password is changed, a command similar to the following should be used to change the credential set:
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions RM: Importing Requirements
This demonstration show you how to import requirements from CSV, Microsoft Word, and Microsoft Excel files to Dimensions RM.
Dimensions CM: Introduction to streams (demonstration)
This demonstration introduces Dimensions CM streams.

Additional Assistance

  • Submit a Case Online
  • FAQs