Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,931
Community Members
 
Community Events
176
Community Groups

Send web request action of Automation for Jira with credentials

I like the Send web request action of Automation for Jira.
https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828

It could be very helpful to integrate Jira with other systems.
It's simple but very powerful.

Almost all systems need authorization. So we have to input credentials in the form.
However, it seems there's no way to mask credentials in the form. So I can't use it in many use cases.

https://jira.atlassian.com/browse/JSWCLOUD-22729

How are you using the Send web request action without the masking parameter feature?
You find workarounds? Or put credentials as plain text? Or give up to use it?

2 comments

I was with the same problem that you have, my "workaround" is using user properties to store both user and password, and then, using smart values to access the values. 

I have admin privileges, so I created the properties through this end point and use the user who has the properties as the actor of the rule, then I can access its values with

 {{rule.actor.properties.prop_name.username}} and {{rule.actor.properties.prop_name.password}}


I'm not satisfied with this yet, but I think this is less dangerous than writing down the password everywhere.

Pros

  1. Password is not a visible text
  2. You can use in all projects
  3. You have to know what are the properties to get the access through automation 
  4. You need User Management privileges to access through API 

Cons

  1. The values can be printed by anyone who was automation access and know the user and the properties that have the info. 
  2. The values can be access through API

 

I hope I could help you some way

@luannagobbato 

Thank you for sharing your workaround.
I agree with you about the Pros and Cons.

I forgot to leave a comment.

Jira automation supported masking HTTP headers.
So, we don't have to bother with this topic anymore.

Comment

Log in or Sign up to comment