# Encryption of "shared secret" database column

**URL:** <https://forum.inductiveautomation.com/t/encryption-of-shared-secret-database-column/62977>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [August 13, 2022, 8:18am UTC](https://forum.inductiveautomation.com/t/encryption-of-shared-secret-database-column/62977 "2022-08-13T08:18:08Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\
**Post date:** [August 13, 2022, 9:55am UTC](https://forum.inductiveautomation.com/t/encryption-of-shared-secret-database-column/62977/2 "2022-08-13T09:55:25Z")

</div>

> [@Best practice for an API key](https://forum.inductiveautomation.com/t/best-practice-for-an-api-key/36088/7):
>
> If anyone’s interested in learning a bit about Java development, you can refine this proof of concept I just whipped up: It adds a new section to the config page of the gateway that lets you define named secret values, and then (within the gateway scope) you can run system.secrets.getSecret(\<name\>) to retrieve the un-encoded value.

---

_[View the full topic](https://forum.inductiveautomation.com/t/encryption-of-shared-secret-database-column/62977)._
