DBeaver Master Password and PostgreSQL Credential Rotation Interoperability

DBeaver utilizes a master password to encrypt stored connection credentials via AES-256, preventing clear-text exposure in the global preferences file. This mechanism secures the local storage of credentials before they are forwarded via the JDBC driver to the database's native authentication subsystem.

A challenge arises when credentials are rotated or expire on the PostgreSQL server independently of the DBeaver client. Because the tool relies on the encrypted local store to initiate the handshake, there is no native trigger to synchronize these changes without manual user intervention.

Given this architecture, what is the expected behavior when a PostgreSQL password expires while DBeaver is configured with a master password? Does the JDBC driver provide a mechanism to signal the client to prompt for new credentials, or must the encrypted store be manually updated for every affected connection?