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 SBM 10.1 - 10.1.1.3: How to generate new signed certificate trust keys for SBM and copy them to additional servers as needed (Generating SSO certificates)
To secure your installation, you must generate new key new key pairs. If you do not generate new key pairs, then the default certificates that the STS inherently trusts are used. To increase security you should generate a new unique certificate for each SSO component.
CMS-XML DimCM: SSO: How to create standalone SSO certificates for Dimensions CM and establish a trust with the SSO Server
1. Checking if SSO with CAC is enabled. 2. How to check the expiry date for an existing certificate . 3. Generating A New Certificate
CMS-XML "Unspecified STS Error" after upgrading to SBM 10.1.2
The most common scenario involves the use of Serena SSO/Common Access Card (CAC) or SSO/PIV Card or SSO/PKI client certificates. Client certificate setups typically uses the X509-base or X509-LDAP SSO authenticators which access a java keystore (JKS) to verify trust of a client certificate . The default setup uses a JKS called SERENACA.JKS.
CMS-XML Expiring Certificate for Dimensions CM on August 9th 2014 - this will result in "PRG7700117E Error: Untrusted endorsing credentials" when logging into the Desktop Client
How to resolve Please go to article S140601 to generate a new key and establish a trust with the SSO Server.
CMS-XML How to install an SSL certificate into the RLC 5.x/RLM 4.x/ALM 3.x JRE keystore for Serena Common Tomcat
When prompted for a password, enter "changeit". If you are prompted or override or trust the certificate , enter yes. Restart Serena Common Tomcat and test the process you were working on.
CMS-XML 12.2.0.2 : Certificate on automatic Promote/Deploy
12.2.0.2 : Certificate on automatic Promote/Deploy
CMS-XML SBM configurator eroniously report that Default certificates provided by Serena have been detected
SBM configurator eroniously report that Default certificates provided by Serena have been detected
CMS-XML SBM SSO SSL Integration with Version Manager - Configurator will not take certificate
SBM SSO SSL Integration with Version Manager - Configurator will not take certificate
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.
CMS-XML DIM CM: One-time login certificate which includes a tertiary node login (MVS) fails if the @ is in login credentials
DIM CM: One-time login certificate which includes a tertiary node login (MVS) fails if the @ is in login credentials
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs