Uploaded image for project: 'Automation for Jira'
  1. Automation for Jira
  2. JIRAAUTOSERVER-335

Add support for secret storage

    XMLWordPrintable

    Details

    • Type: Suggestion
    • Status: Gathering Interest (View Workflow)
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: Configuration
    • Labels:
      None
    • Feedback Policy:

      Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Description

      A4J does not support secret storage. The obvious use case for storing a secret would be for outgoing webhooks, where someone might require an API token in the custom request headers. https://codebarrel.atlassian.net/browse/AUT-2230 solves a specific case of this for first-party clients, but does not explicitly require the implementation of secret storage, so this ticket has been created instead.

      An ideal outcome would be a way for users to securely add and remove secrets per automation rule or project, similar to Bitbucket Pipelines variables (which are encrypted at rest), which can then be referenced from within automation rules

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              cmarriott Charlie Marriott
              Votes:
              2 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated: