MIP File SDK Failing to Label Certain PDF Files

Question

We're running into an issue with the MIP File SDK where certain PDF files that are not signed are failing to apply labels with CommitAsync. The specific error is "file_commit_async Failed with: [NotSupportedError: 'The file is protected by signature, CorrelationId=6679cd55-6695-43ea-b27b-d3a6e3ed34e3, CorrelationId.Description=FileHandler'".

We noticed this after updating from 1.13.161 to 1.14.108. I've attached a sample file here that can be used to reproduce the issue.

sample.pdf

Answer 1

Hi @Dan Walsh
Thanks for the question and using MS Q&A platform.

The error message you are encountering, "file_commit_async Failed with: [NotSupportedError: 'The file is protected by signature...'", suggests that the PDF file you are trying to label is digitally signed. According to the context, the MIP SDK does not support labeling signed PDF files, which could be the reason for the failure after your update to version 1.14.108.

Please check the below image for reference:

To resolve this issue, you may want to check if the PDF files are indeed signed or if there are any other protections applied to them. If they are not signed, you might need to ensure that the MIP SDK is correctly configured and that you are using the appropriate methods for labeling.

Reference: New support for PDF encryption with Microsoft Information Protection

• Microsoft Information Protection (MIP) SDK FAQs and issues
• Microsoft Information Protection (MIP) Software Development Kit (SDK) version release history and support policy

Hope this helps. Do let us know if you have any further queries.