-
Suggestion
-
Resolution: Unresolved
-
None
-
3
-
9
-
It's great that Jira Automation allows teams to configure outgoing webhooks as an action, but it is very likely these outgoing calls will need authentication, stored as a header.
Customers would like to know these authorization headers are not stored in plaintext, but rather encrypted or hashed on their way to the database.
- mentioned in
-
Page Failed to load
I would expect Jira Automation should be able to encrypt a token with sha1/sha256, then the receiver would have to decrypted with the body of the message like Trello does it right now,
https://developer.atlassian.com/cloud/trello/guides/rest-api/webhooks/#webhook-signatures
This would make sure there is unique hashed tokens over the wire.