Uploaded image for project: 'Automation for Cloud'
  1. Automation for Cloud
  2. AUTO-182

Support additional auth types for incoming and outgoing webhook components, e.g. to support GraphQL Actions, NTLM auth, OAuth for use with Google APIs, MATLS support

XMLWordPrintable

    • 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.

      Suggested improvements

      • With some of the Atlassian API's seeming moving from REST to Graphql (like the Compass product), it would be good for the automation product to be able to support graphql in an outbound matter, as well as respond to graphql updates/mutations for integration with other tools 
      • As of now when we use incoming webhook for Jira automation we do not have any means to authenticate, which can allow anyone to send web requests if they know the URL. We would like to be able to enforce authentication for incoming web requests, credentials for which can be sent in the headers of the web request. The following workaround can be used to add an additional token validation for incoming webhooks: Setting up token validation within Automations using the Incoming Webhook trigger.
      • MATLS support to ensure connection are trusted from Jira Cloud to on-premise CI systems and vice-versa.

              Unassigned Unassigned
              81c43d12e133 Ken Young
              Votes:
              44 Vote for this issue
              Watchers:
              15 Start watching this issue

                Created:
                Updated:
                Resolved: