Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Can we store tokens in one place and use them as smart values in Jira automation web requests?

Prasad Bonthu
Contributor
September 1, 2025

In Jira automation, we are currently passing tokens directly in the web request action. Is there a way to store these tokens in a central location (similar to a CMDB) and then reference them as smart values when making web requests?

This would help us avoid hardcoding tokens in multiple rules and make maintenance easier.

2 answers

0 votes
Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 2, 2025

Hi @Prasad Bonthu 

@Matteo Vecchiato has valid options, you could also use a lookup table in automation to store the tokens

Prasad Bonthu
Contributor
September 2, 2025

I have multiple automation rules where we use different web requests. To simplify maintenance, we want to store the tokens in a centralized location instead of hardcoding them separately in each rule.

Currently, we have CMDB objects created for data maintenance. I was wondering if, apart from CMDB, there are other options to securely manage token data.

Would using a lookup table in Jira automation be sufficient for this requirement, or is there a better approach to centrally and securely store tokens for reuse across rules?

0 votes
Matteo Vecchiato
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 2, 2025

Hi @Prasad Bonthu ,

Thank you for your interesting question.

If you manage differents tokens, you could store the tokens in Assets inside Jira Service Management (it's like a CMDB), in a specific object type. Then, inside automation, you can use the lookup function to query the Assets.

Assets requires a Premium license to be activated.

Another solution is to use an external Key Vault (like Azure vault) and call it from automation though web request.

I hope it helps

Prasad Bonthu
Contributor
September 2, 2025

Thanks for the suggestions. We already have some CMDB objects created to maintain project data, so we’ll plan to use the CMDB to store the API tokens as well.

Appreciate your guidance!

Prasad Bonthu
Contributor
September 2, 2025

@Matteo Vecchiato 
Is there any Object Attribute type in Assets/CMDB that supports storing passwords or secret values in an encrypted way, instead of showing the actual value in plain text?

By default, I don’t see such an option available it mostly supports text, URL, or number types. Is there any recommended approach to securely store API tokens or sensitive data in Assets?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events