# Is there a central Ignition SSL keychain available?

**URL:** <https://forum.inductiveautomation.com/t/is-there-a-central-ignition-ssl-keychain-available/114254>\
**Category:** Module Development\
**Tags:** ignition81, ignition83\
**Created:** [March 2, 2026, 9:29am UTC](https://forum.inductiveautomation.com/t/is-there-a-central-ignition-ssl-keychain-available/114254 "2026-03-02T09:29:17Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![christofer.dutz](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/christofer.dutz/32/76634_2.png) [@christofer.dutz](https://forum.inductiveautomation.com/u/christofer.dutz)\
**Post date:** [March 2, 2026, 9:29am UTC](https://forum.inductiveautomation.com/t/is-there-a-central-ignition-ssl-keychain-available/114254/1 "2026-03-02T09:29:17Z")

</div>

Hi all,

I’m currently working on integrating support for Secure AMS into my Beckhoff ADS driver. Here there are 3 types I can use: Officially Signed Certificates (not an issue), PSK (Pre-shared-Key) and Self-Signed-Certificate. While for the first I obviously don’t need any setup and for the PSK version I just display two input fields, for the SSC I would need a java keychain plus some input fields.

Now I was thinking, I assume the OPC-UA driver supports TLS secured communication, so ignition probably has a keychain in place. I would like to re-use that for my driver. The alternative would be to auto-generate one, if none is provided.

I guess generating one on the fly would not be a huge problem, I just thought re-using what’s already there would be easier.

So … Is there an option for modules to access an official Ignition keychain for TLS transports?

Chris

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [March 2, 2026, 1:02pm UTC](https://forum.inductiveautomation.com/t/is-there-a-central-ignition-ssl-keychain-available/114254/2 "2026-03-02T13:02:59Z")

</div>

There isn’t a centralized KeyStore or certificate management function/area, though it’s something we’ve talked about. Currently each area of Ignition that needs certificates/keys manages its own.

---

<div class="post-metadata">

**Author:** ![christofer.dutz](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/christofer.dutz/32/76634_2.png) [@christofer.dutz](https://forum.inductiveautomation.com/u/christofer.dutz)\
**Post date:** [March 2, 2026, 2:36pm UTC](https://forum.inductiveautomation.com/t/is-there-a-central-ignition-ssl-keychain-available/114254/3 "2026-03-02T14:36:23Z")

</div>

Ah ok … thanks … then I’ll continue down that path … is there a default storage convention where modules are to put their data (such as p12 keystores?)

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [March 2, 2026, 2:49pm UTC](https://forum.inductiveautomation.com/t/is-there-a-central-ignition-ssl-keychain-available/114254/4 "2026-03-02T14:49:11Z")

</div>

From GatewayContext, get the SystemManager.

In 8.1, you can get the data dir and then use something like `$data/$moduleId/yourfiles`.

In 8.3 SystemManager has methods like `getModuleConfigDir()` that you would want to use instead.

---

<div class="post-metadata">

**Author:** ![christofer.dutz](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/christofer.dutz/32/76634_2.png) [@christofer.dutz](https://forum.inductiveautomation.com/u/christofer.dutz)\
**Post date:** [March 2, 2026, 2:59pm UTC](https://forum.inductiveautomation.com/t/is-there-a-central-ignition-ssl-keychain-available/114254/5 "2026-03-02T14:59:57Z")

</div>

Perfect … thank you 🙂