Encryption Library: User-defined EncryptorField aliases are not used

🧵 Story

A user reported a bug in the forums where providing multiple Encryptor keys in their POCOs would throw an error "Missing encryptor for alias ‘’" upon serializing their document before being sent over the network.

This seems to be caused by a mixup during changing from LegacySigningKeyName to the new KeyName:

• The EncryptedFieldContractResolver which only looked at the Attribute's LegacySigningKeyName and passed it to the EncryptedFieldConverter (which is null by default).
• The EncryptedFieldConverter which did not pass the _legacySigningKeyName in the method parameters of ICryptoManager.Encrypt

Meaning using a custom key alias e.g. [EncryptedField(KeyName = "customKey")] would make the library replace it with the default "_DEFAULT_".

🛠️ Acceptance Criteria

Multiple custom key names.

📚 Resources

• Forum post
• Field encryption library on GitHub