# Using jre from third party

**URL:** <https://forum.inductiveautomation.com/t/using-jre-from-third-party/93249>\
**Category:** Ignition\
**Created:** [July 15, 2024, 6:16pm UTC](https://forum.inductiveautomation.com/t/using-jre-from-third-party/93249 "2024-07-15T18:16:10Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jakned](https://avatars.discourse-cdn.com/v4/letter/j/4da419/32.png) [@jakned](https://forum.inductiveautomation.com/u/jakned)\
**Post date:** [July 15, 2024, 6:16pm UTC](https://forum.inductiveautomation.com/t/using-jre-from-third-party/93249/1 "2024-07-15T18:16:10Z")

</div>

Hi, i was wondering if one could use .jre to extend Ignition functionality. I wanted to use JWTs for securing my webdev APIs and there is a Java package for that on Maven.

I have some other use cases in mind as well.

Would that be possible?

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [July 15, 2024, 6:39pm UTC](https://forum.inductiveautomation.com/t/using-jre-from-third-party/93249/2 "2024-07-15T18:39:39Z")

</div>

Using [**jar**](https://en.wikipedia.org/wiki/JAR_(file_format)) files from scripting is _possible_, but explicitly unsupported. The only **supported** avenue to bundle an arbitrary jar is to provide an entire custom module and expose the third party dependency's functionality via a system function or some other hook.

That said, if you search this forum you can find the directory on the gateway where you can drop arbitrary .jar files, and, upon restarting the gateway, they will be accessible to scripting in the matching scope(s), depending on exactly which directory you dropped the files in.

I'm being deliberately obtuse because this isn't a recommended option, and can cause you maintenance pain if you construct your entire system _silently_ relying on an infrequently/never updated external dependency.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [July 15, 2024, 6:41pm UTC](https://forum.inductiveautomation.com/t/using-jre-from-third-party/93249/3 "2024-07-15T18:41:18Z")

</div>

> [@paul-griffith](#):
>
> external dependency

**Especially** one that gets blown away whenever you upgrade Ignition.

---

<div class="post-metadata">

**Author:** ![jakned](https://avatars.discourse-cdn.com/v4/letter/j/4da419/32.png) [@jakned](https://forum.inductiveautomation.com/u/jakned)\
**Post date:** [July 15, 2024, 7:10pm UTC](https://forum.inductiveautomation.com/t/using-jre-from-third-party/93249/4 "2024-07-15T19:10:16Z")

</div>

What exactly happens here? Do the packages get deleted when upgrading?

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [July 15, 2024, 7:12pm UTC](https://forum.inductiveautomation.com/t/using-jre-from-third-party/93249/5 "2024-07-15T19:12:47Z")

</div>

The folder(s) in question literally make up Ignition. By definition, an upgrade wipes out anything old and replaces it with the dependencies from the new version of Ignition. They _might_ be identical, and often are, but they're always fully included for the sake of correctness.