-
Suggestion
-
Resolution: Duplicate
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.
- duplicates
-
AUTO-4 More authentication options for outgoing webhook "Send web request" component and "Incoming webhook" trigger- e.g. to support GraphQL Actions, NTLM auth, OAuth for use with Google APIs, MATLS support, HMAC Support
- Gathering Interest
- is duplicated by
-
AUTO-23 More authentication options for Incoming WebHook generated by Jira automation - option to enforce authentication
- Closed
-
AUTO-648 Support NTLM auth for outgoing web requests
- Closed
- mentioned in
-
Page Loading...