Secure storage of API keys used across multiple automations?

[David Foote]

Hi all,

Not sure if there even is a solution to this, but we have several automations that need to call the Jira API. This results in us storing our API key in each automation. We do utilize the 'hidden' attribute that prevents the key from being exported along with the rest of the automation.

When our API key expires, we'll have a lot of automations to update to the new key. It would be really nice if there was some secure key/value store that we could update instead...

How is everyone else handling this?

[Vikrant Yadav · Accepted solution]

Hi @David Foote 

In our case, we have created an API Token Register in Confluence, where we keep a record of each API token mapped with the corresponding Jira Automation rule. The register includes details such as the creation date, expiry date, automation rule name, and rule URL.

All API tokens are securely stored in 1Password.

Since Atlassian does not provide an API to generate new tokens, new tokens can only be generated via the UI.