Skip to main content
Inspiring
Nov 13, 2026 12:57 AM UTC
Answered

Is Adobe code signing required for a plug-in broker if "Use only Certified plug-ins" is off?

Hi,

We are moving an Acrobat (Windows) plug-in to work with Protected Mode, because Protected Mode
becomes mandatory on Windows in December 2026. We plan to use Sandbox Broker Extensibility
and place our broker in <Acrobat>\plug_ins\pi_brokers\.

The Sandbox Broker Extensibility page says the broker binary and its API description must be submitted to Adobe for code signing, and that the signature is verified when"Use only Certified plug-ins" is enabled.

Questions:
1. If "Use only Certified plug-ins" is disabled, will an unsigned broker in pi_brokers launch normally?
2. Will this stay the same after Protected Mode becomes mandatory in December 2026?
3. How do third-party developers submit a broker for code signing? Is there a contact or a form?
   (Another page says there is currently no way for third-party plug-ins to be certified,so we are not sure whether broker signing is available.)

Thank you.
 

CORCTON34033231
CORCTON34033231Correct answer
Community Expert
Nov 13, 2026 3:18 AM UTC

Hi momomo_9987 — on your first question, the answer is no, based on Adobe’s own Sandbox Broker Extensibility doc. It says the signature of the plug-in broker executable is verified before launch if the “Use only Certified plug-ins” option is enabled — so with that option off, the signature isn’t verified and an unsigned broker in pi_brokers should launch normally. The same doc also says processes placed in <Acrobat>\plug_ins\pi_brokers are whitelisted there.

Doc: https://opensource.adobe.com/dc-acrobat-sdk-docs/library/overview/SandboxBrokerExt.html

A related 2024 thread on the same topic was marked Answered, with the expert noting Adobe code signing is only necessary for plug-ins used in Reader: https://community.adobe.com/questions-18/do-all-acrobat-acrobat-plugins-that-use-a-broker-in-protected-mode-need-to-be-certified-610123

On your third question, the doc says the broker binary and its API description must be submitted to Adobe for code signing, but it doesn’t give a public contact or form that I could find — the Acrobat SDK forum would be the best place to ask Adobe for the submission route.

On your second question, I can’t confirm from the doc whether anything changes when Protected Mode becomes mandatory in December 2026, so I won’t guess — worth keeping an eye on the SDK doc.

 

 

 

 

2 replies

CORCTON34033231
Community Expert
CORCTON34033231Community ExpertCorrect answer
Community Expert
Nov 13, 2026 3:18 AM UTC

Hi momomo_9987 — on your first question, the answer is no, based on Adobe’s own Sandbox Broker Extensibility doc. It says the signature of the plug-in broker executable is verified before launch if the “Use only Certified plug-ins” option is enabled — so with that option off, the signature isn’t verified and an unsigned broker in pi_brokers should launch normally. The same doc also says processes placed in <Acrobat>\plug_ins\pi_brokers are whitelisted there.

Doc: https://opensource.adobe.com/dc-acrobat-sdk-docs/library/overview/SandboxBrokerExt.html

A related 2024 thread on the same topic was marked Answered, with the expert noting Adobe code signing is only necessary for plug-ins used in Reader: https://community.adobe.com/questions-18/do-all-acrobat-acrobat-plugins-that-use-a-broker-in-protected-mode-need-to-be-certified-610123

On your third question, the doc says the broker binary and its API description must be submitted to Adobe for code signing, but it doesn’t give a public contact or form that I could find — the Acrobat SDK forum would be the best place to ask Adobe for the submission route.

On your second question, I can’t confirm from the doc whether anything changes when Protected Mode becomes mandatory in December 2026, so I won’t guess — worth keeping an eye on the SDK doc.

 

 

 

 

Translate
Inspiring
Nov 13, 2026 9:37 AM UTC

Thank you for the clear answer and for pointing me to the exact passage in the Sandbox Broker Extensibility doc. That resolves my first question.

Two follow-up questions, if anyone knows:

  1. Can administrators enforce "Use only Certified plug-ins" through FeatureLockDown or another policy? If so, I assume an unsigned broker would fail to launch in those environments, so we would need to get it signed before shipping to enterprise customers.
  2. To confirm my understanding: signing the broker exe is separate from Reader-enabling the plug-in itself. If the 64-bit unified app starts in Reader mode, an unsigned plug-in still causes the "Invalid plugin detected" error, even if its broker is signed. Is that correct?

I'll also ask on the Acrobat SDK forum about the submission route for code signing.

Thanks again!

Translate