Unable to get local secret Flyway Desktop

You are seeing this error message in Flyway Desktop:

Unable to get local secret Flyway Desktop d43d01-40e4-480c-aef6-c3344b531886 
Caused by: Error reading secret: Element not found.

It means the local secret store on the host machine doesn't have a record of the secret that is referenced.

The most likely causes are:

• The project was created on another machine and the secret was stored on that machine
• You have duplicated a project file and then edited it
• The local credential store has been modified or your access has changed

In the first two instances, simply re-establishing the database authenticating in the Flyway Project will update the project file and resolve the problem. In the last instance, please liaise with your IT security team.

If your goal is to share a flyway project file with your colleagues, it's easier to remove the user secret password reference from the .TOML file so that they're prompted to supply their own when importing and using the project file.

OS Specific credential stores

In the event you wish to also copy the credentials rather than require users to repopulate them, the credential stores used are as follows:

Windows
The Windows Credential Manager is used. The secret must be stored as a password field inside a "Generic Credential" under "Windows Based Credentials".

Linux
Libsecret is used, if available. The resolver will look in the default keychain. The resolver will match against the following secret schema:

product: Flyway 
version: 1

Mac
The Mac keychain will be used. The secret will be read as a generic password (find-generic-password) with a service name ("Keychain Item Name") of Flyway. The key used by the secret resolver will be the account name for the keychain item.