# Storing Tokens Securely **URL:** \ **Category:** Ignition\ **Created:** [June 18, 2021, 11:45am UTC](https://forum.inductiveautomation.com/t/storing-tokens-securely/47941 "2021-06-18T11:45:14Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![bkarabinchak.psi](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bkarabinchak.psi/32/83567_2.png) [@bkarabinchak.psi](https://forum.inductiveautomation.com/u/bkarabinchak.psi)\ **Post date:** [June 18, 2021, 2:17pm UTC](https://forum.inductiveautomation.com/t/storing-tokens-securely/47941/2 "2021-06-18T14:17:14Z")
> [@Best practice for an API key](http://forum.inductiveautomation.com/t/best-practice-for-an-api-key/36088/5): > > Some previous discussion around this in this thread: In general, the most important thing is to limit the scope of where you secret can possibly be read from. There’s some filesystem based suggestions in that thread that are good practice. Environment variables can work, but aren’t guaranteed to be as isolated as you might like them to be, as @pturmel points out in that thread. Ideally, anything interacting with an API would eventually become an Ignition module - in that case, you can stor… --- _[View the full topic](https://forum.inductiveautomation.com/t/storing-tokens-securely/47941)._