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 create and update the SSO STS certificate in Dimensions CM
How to create and update the SSO STS certificate in Dimensions CM
CMS-XML Dim2009R2: SSO CAC: Certificate principal not found in LDAP
Dim2009R2: SSO CAC: Certificate principal not found in LDAP
CMS-XML How to verify that the SSO Certificate Revocation List (CRL) files are being used
How to verify that the SSO Certificate Revocation List (CRL) files are being used
CMS-XML DimCM: SSO: How to create standalone SSO certificates for Dimensions CM and establish a trust with the SSO Server
DimCM: SSO : How to create standalone SSO certificates for Dimensions CM and establish a trust with the SSO Server
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
HSSO - Hybrid SSO for SaaS environments- cannot logon as getting Untrusted Endorsing Credentials or Failed to verify signature - certificates expired and need updating
CMS-XML SBM 2009 R4 (and prior): How to generate new signed certificate trust keys for SBM and copy them to additional servers as needed (Renew SSO certificates)
SBM 2009 R4 (and prior): How to generate new signed certificate trust keys for SBM and copy them to additional servers as needed (Renew SSO certificates )
CMS-XML Version Manager SSO: Default Certificates for STS, GATEKEEPER and VMSERVER expire starting June 13th 2015
This article is applicable only if you are running Version Manager 8.4 or newer and have Project Databases configured to use the SSO /CAC Login Source. To validate, perform the following steps: Open the VM Desktop Client
CMS-XML Utility to update the SSO (Serena Single Sign-On) certificates used by PVCS Version Manager
This article is applicable only if you are running Version Manager 8.4 or newer, have Project Databases configured to use the SSO /CAC Login Source and are connecting to a Version Manager SSO server. To validate, perform the following steps: Open the VM Desktop Client
CMS-XML Cannot read/write SSO certificates in case both SSO encryption and non-default keystore password
Cannot read/write SSO certificates in case both SSO encryption and non-default keystore password
CMS-XML Dim2009R2: SSO CAC: Invalid User Name or Password or ACL7700119E Cannot confirm certificate authenticity
When using the Web Client with SSO CAC enabled, the following error is occurring for some users on login: Invalid User Name or Password
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs