EXAOperation displays invalid fingerprint

Details

Detail name Value
Changelog Number 13103
Type Bug
Status Open
Affected Versions

Description

After uploading a custom TLS certificate a database restart is required to make this change effective.
However, EXAOperation immediately shows the new fingerprint even though it is not yet available.

Workaround

Restart the database after uploading a custom TLS certificate.

Fix

An updated fingerprint is only shown after restarting the database.