Yes, GroupDocs.Signature for .NET now supports embedding custom objects as metadata signature in the images. So you can now sign the images with your desired metadata properties. We have introduced this feature in version 19.6 by adding a new public method AddSignature to the ImageMetadataSignOptions class. Not only this, but you can also apply the data encryption to the custom objects. So let’s check out how easy it is to sign an image with custom metadata signature.
Before jumping to the code, let me first describe the steps that are required to embed the encrypted custom objects.
- Configure the storage paths, create and populate the object of SignatureConfig
- Instantiate the SignatureHandler by passing SignatureConfig object
- Setup IDataEncryption object with new SymmetricEncryption()
- Setup the custom object with the desired data members
- Add the custom object to the metadata signature list using AddSignature method
- Apply the data encryption
- Sign the document
That’s it and the image has been signed with your desired metadata. Let’s now have a look at the code sample for completely understanding the working of this feature.
Along with this feature, we have also added a notable improvement in the searching process. With this improvement, you will now be able to locate the document’s page number where the signature object was found. For this, the public abstract class BaseSignature has been extended with a new property PageNumber. This is how you can achieve it using the code.
Listed below are the other improvements and the bug fixes that we have packaged in version 19.6.
Improvements
- Ability to verify files with .cmx (CorelDraw) format as image documents
- Ability to search .cmx (CorelDraw) files as image documents
- Ability to sign .cmx (CorelDraw) files as image documents
- Ability of saving Word documents with FlatOpc formats
- Support of .cdr (CorelDraw) file format for verification process
- Ability to search .cdr (CorelDraw) files as image documents
- Ability to sign .cdr (CorelDraw) files as image documents
Bug Fixes
- Digital Signature’s IsValid property is not being set correctly for the Search routine
- Output file is missing if save options are not provided
- Illegal character issue when trying to encrypt serialized data
- The output file’s path is unexpected for different scenarios
Alright! So this is it from my side and now, it’s your turn to download and check out the latest release. For more details, you can have a glance at the release notes. I would also recommend you consult the Developer’s Guide while evaluating the API’s features. Still, if you need any assistance, please feel free to write to us on our forum.
