Skip to main content
K
Kapil5C43
Participant
May 14, 2021
Question

Need to create DRM plug-in for Acrobat Reader using Acrobat SDK

  • May 14, 2021
  • 1 reply
  • 2593 views

We’re looking to build an Adobe Reader plug-in to open DRM protected PDF files. We read about the Acrobat Reader Integration Key License Agreement (RIKLA) and related material from here. However, we’re not clear about the specific steps to set up a strategic partnership with Adobe to create DRM plug-ins and pricing details. The link given for “digital rights management (DRM) Acrobat Reader plug-in” is broken.

 

How do I go about creating a DRM plug-in? The steps are unclear. The email address provided on the above mentioned page does not seem to reply. There is no other Adobe Dev Support contact I have to contact Adobe.

This topic has been closed for replies.

1 reply

T
Test Screen Name
Legend
May 14, 2021

Well, you'd start by making a DRM plug-in that worked with Adobe Acrobat. That is the basic start for all Reader plug-ins.

 

The last time there was a page it talked about $25K or $50K per annum as typical for DRM, from what I remember. Anyway, https://opensource.adobe.com/dc-acrobat-sdk-docs/devnet/rikla.html gives an email you WILL need to contact to navigate the process. I suspect Adobe demand serious oversight so they can do quality control on your DRM. There are historical reasons for their great care.

MikelKlink
MikelKlink
Participating Frequently
May 16, 2021

@Test Screen Name - Out of interest:

quote

There are historical reasons for their great care.

Can you expound?

T
Test Screen Name
Legend
May 16, 2021

This is my recollection, with no inside knowledge. Years ago, Adobe created PDF encryption and they created plug-ins. They created a sample plug-in with some token (worthless) encryption as a way of showing what could be done, and where the real encryption would be.  Someone took the sample and turned it into a "real" security product by changing the name, but not replacing the worthless sample encryption with any actual security. So far, so good. But what happened next was surprising: Adobe got the blame for this. Their reputation was damaged, actually quite badly.


So there we are, there's one theory. Another theory is that Adobe see that people are using DRM to protect valuable stuff, and don't see why - since they do most of the work by making Acrobat Reader - they shouldn't get a big cut of the action.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices