Certificate Mismatch Error

The Certificate Mismatch error dialog is displayed if the Rhapsody engine presented a valid self-signed SSL certificate. This self-signed certificate, however, is different to the certificate that has been previously used to connect to this engine. This is the expected behavior if the Rhapsody engine's certificate has been changed to a new self-signed certificate. However, care must be taken when you encounter this scenario as it may mean an attacker is attempting to impersonate the Rhapsody engine and intercept your communications.

We strongly recommend that you manually verify the SSL certificate before using any available workarounds. This is done by comparing the certificate thumbprint, shown in the following screenshot, to the certificate thumbprint stored on disk on the Rhapsody server in the <Rhapsody>/rhapsody/ide.sha1.txt file. If these thumbprints match, then the certificate can safely be trusted; if they do not match, then the connection should be aborted as it is not the expected SSL certificate.

If it is the Rhapsody engine's SSL certificate that has been changed, then the Rhapsody IDE Trust Manager can be used to remove the old reference to this Rhapsody engine, and then re-established the connection. A warning dialog is still displayed afterwards (because the Rhapsody IDE would effectively be connecting to the Rhapsody engine with a self-signed certificate for the first time), but the SSL certificate can now be accepted.