Storing Encrypted Settings Per-Action

[fhollermayer]

The documentation states that secrets, like API keys and such, should be handled as Global Settings. In my specific use case, one action is linked to one host. What are my options to safely store corresponding credentials?

Do I need to handle input and blur events in the PI myself and setup a map<action_id, settings_object> that i manually push into the global settings API?

[ChekTek]

Hi @fhollermayer

Yes, for storing things like credentials, you'll want to stick to global settings. A map of the action ID and settings is probably your best solution at this time. Regular settings are written as plain text to the file system which would not be a safe way to store credentials, while global settings are stored securely.