Hi all,
I am trying to use Public Encryption Keys to encrypt 3 fields on my form. It works great until I attach a file to the document (doesn’t matter whether the RichText field containing the attachment is set for encryption or not). After I save, the regular $SealData fields are gone and the supposedly encrypted fields are visible in the Document Properties of the view. I open the document again, remove the attachment, resave - the $SealData fields are there as expected, encrypted fields are hidden. I am attaching the file through the UI - no LotusScript code anywhere to manipulate the fields, attach the file, set the encryption, etc.
This behavior is very consistent and happens in the 7.0 client, too. I even downloaded the Sandbox template on using encrypted fields, to rule out anything weird I might be doing. Nope, happens there, too. Attachments break the encryption on the document even though the SEAL flag is still there.
It seems like the old bug of the attachment getting encrypted inappropriately has made way for a new regression bug where the attachment gets encrypted, but the other fields do not.
If you are using encryption in your database design right now, see if you can reproduce this issue. I’d love to know. I’ll be chatting with IBM tomorrow.
Thanks!