Does UXP Block Self‑Signed HTTPS for Internal Development?

Premiere Pro
1

Hi Adobe Team,

I need clarification on UXP’s network restrictions.

Right now it seems UXP does not allow:

  • HTTPS requests using self‑signed or internal CA certificates

This makes it difficult to develop and test plugins that rely on internal APIs that are not publicly exposed.

Could you please confirm:

  1. Is it correct that UXP does not support self‑signed/internal‑CA HTTPS?

  2. Are there any plans to support this in the future?

  3. Is there an official workaround that doesn’t require making internal APIs publicly trusted?

It would be great to know how developers handle environments where exposing internal services publicly is not possible.

Thanks!

2

Had a similar question a few month back when I start playing with UXP (see question at the bottom of Allowing Network access to a specific PORT? “maybe UXP require to have a non-self signed cert ?“ )

…but did not get any answer.
Hopefully you’ll be more lucky than me and get one :wink:

3

@bbb_999 : Bruce any insight on this ?

Is this a known bug ? Is there a fix coming at one point (or not in radar / too low priority ) ?

Known limitation to enforce more security (Hmmm… probably not, restricting access to specific site & https is already available from manifest, sounds more strict anyway).

This is really painful not to be able to test locally without a real / not self-signed cert.

1 Like
4

In my use-case, the API the extension needs to call is only reachable from within the internal infrastructure. For security reasons, it cannot be exposed publicly.

With the CEP version, we worked around this by using Axios and attaching our internal CA certificate through the HTTPS agent.