Uploaded image for project: 'Tika'
  1. Tika
  2. TIKA-3666

Detect and indicate file encrypted with Rights Management Service RMS/IRM

Agile BoardAttach filesAttach ScreenshotVotersStop watchingWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 2.9.0
    • metadata
    • None

    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

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            tallison Tim Allison
            4U6U57 August Valera
            Votes:
            1 Vote for this issue
            Watchers:
            7 Stop watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment