[TIKA-3666] Detect and indicate file encrypted with Rights Management Service RMS/IRM

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.9.0
• Component/s: metadata
• Assignee: Tim Allison
• Reporter: August Valera
• Created: 31/Jan/22 20:01
• Updated: 28/Aug/23 19:25
• Resolved: 20/Jun/23 19:10

Description

Rights Management Service (RMS), implemented in MS Office as Information Rights Management (IRM), allows organizations to set file permissions that are stored within the file. In most cases, this will result in the file getting a new extension (with a prefix p, such as .txt becoming .ptxt), but in the case of MS Office and PDF files, which support this natively, the implementation results in the file contents being encrypted without any extension change. 

Current behavior

Running such files through Tika produces results as if it was an empty file ran through DefaultParser and OfficeParser.

Expected behavior

Extract more metadata about necessary permissions to view (if possible), and throwing EncryptedDocumentException as is the case with Office files encrypted in the more traditional manner.

Reference: https://docs.microsoft.com/en-us/azure/information-protection/rms-client/clientv2-admin-guide-file-types#supported-file-types-for-classification-and-protection

Issue Links

• is related to: TIKA-4082 Extraction from Microsoft Sharepoint protected PDFs doesn't expose exception like other parsers.
• links to: GitHub Pull Request #1204
• links to: Microsoft: Azure Information Protection Documentation - Supported file types for classification and protection