Encryption passwords that are stored in FMS (via the “Save Password” checkbox shown below) seem to be erased when an OttoFMS deployment is performed. Otto opens the files just fine after a deployment, but after a non-Otto-related restart the files stay closed and the logs show
SECURITY: Database "database" could not be opened: incorrect encryption password.
Once I open one, save the password, and open the rest, reboots work as normal.
Is OttoFMS “clearing” the encryption password?
Hey @Tobias ,
We are aware of this issue. OttoFMS is actually saving the encryption key by default when reopening the file, but there appears to be a bug in FileMaker where the encryption key will not be properly saved since the file has been replaced. I suspect that it has to do with the internal ID of the file changing in FileMaker, and the key is being set improperly. We’re looking for workarounds for the issue but we have been unable to find a solution yet. It seems to happen intermittently and the issue doesn’t rear its head until a restart of FileMaker. I’ll keep you updated if I find a solution for this. Thanks for the report!
-Kyle