| |
Results |
|
VM: How to import an updated SSO STS Trust Certificate / How to solve "Invalid SSO token" errors
|
VM: How to import an updated SSO STS Trust Certificate / How to solve "Invalid SSO token" errors
|
|
|
|
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!
|
|
|
|
See repeated errors in sso-idp.log about the following "Trusted certificate expired and will be discarded: CN=Serena Version Manager Server..."
|
RPConfig.isTrustedEndorser(594): Trusted certificate expired and will be discarded: CN=Serena Version Manager Server, O="Serena Software, Inc.", L=Redwood City, ST =California, C=US If you do use the Integration with SBM and Version Manager see this kb doc for more information S141200 If you don't use the integration between SBM and Version Manager and you want to get rid of this error do the following.
|
|
|
|
SBM 10.1.1.4+ and SBM 11.x: How to generate new signed certificate trust keys for SBM and copy them to additional servers as needed (Generating SSO certificates)
|
The 'Serena SSO IdP' certificate that is used by SSO STS expires in 2 month(s). You must update this certificate before it expires.
|
|
|
|
How to get a copy of the certificate chain and copy it to the certificate trust store ("PKIX path building failed" or similar SSL connection errors.)
|
How to get a copy of the certificate chain and copy it to the certificate trust store ("PKIX path building failed" or similar SSL connection errors.)
|
|
|
|
For SBM versions 11.0 to 11.6.1, the default sample SBM Certificates for STS, Federation Server and SSO Gatekeeper expire on 15th June 2020.
|
**** Warning: Expired SSO certificates will prevent login even if you are running SBM Sessions. ****"
|
|
|
|
Certificate validation failed: Path does not chain with any of the trust anchors in sso-idp.log file.
|
If you are setting up SSO with CAC you may get the following error in the sso-idp.log file. This error indicates the client certificate path hasn't been imported into the idp truststore correctly.
|
|
|
|
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
|
|
|
|
Using Version Manager with a custom SSL certificate - How to change the SSL certificate used to access Tomcat via HTTPS
|
Create a certificate for Tomcat in ... ... of days this certificate should be valid ... ... self-signed certificate that matches your ... Note that this certificate still requires a ... ... To sign your certificate , continue with ... If your Certificate Authority is not ... , add its certificate to the keystore ... ... =Hillsboro, ST =OR, ... ... =Hillsboro, ST =OR, ... Certificate fingerprints: ... =Hillsboro, ST =OR, ... Trust this certificate ? Certificate was added to ... Generate a Certificate Signing Request file for the server certificate . ... return the signed certificate (TomcatCert. ...
|
|
|
|
VM 8.6+: Using certtool to generate an SSL certificate for the PVCS VM Web Application Server (Tomcat) that is signed by your Certificate Authority
|
... create a unique certificate for the default ... ... to hold the Certificate Signing Request and the signed certificate . ... , create the Certificate Signing Request by ... PVCS Certificate Manager (CertTool ... Certificate was added to ... Certificate signing request was ... The generated Certificate Signing Request file ... ... to the desired Certificate Authority. A signed certificate in the file ... The public certificate of CakeWare in ... If your certificate was signed by ... put its public certificate file into this ... as the public certificate files of all ... with the Root Certificate Authority). ... Import the signed certificate by executing:
|
|
|
