Uploaded image for project: 'Automation for Cloud'
  1. Automation for Cloud
  2. 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

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 inbound and 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.
      • Support for OAuth with Automation for Jira. Currently this is not supported and it would be great to have this implemented, for example with using Google APIs for Send Web Request Actions, as Google APIs only support OAuth.
      • Confirm if it's also possible to support HMAC based authentication for both inbound and outbound web requests .

            [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

            Mario Corona made changes -
            Description Original: *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 inbound and 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|https://community.atlassian.com/t5/Automation-articles/Setting-up-token-validation-within-Automations-using-the/ba-p/2733749#M1695].
             * MATLS support to ensure connection are trusted from Jira Cloud to on-premise CI systems and vice-versa.
             * Support for OAuth with Automation for Jira. Currently this is not supported and it would be great to have this implemented, for example with using Google APIs for Send Web Request Actions, as Google APIs only support OAuth.
             * Confirm if it's also possible to support HMAC based authentication for both .             		New: *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 inbound and 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|https://community.atlassian.com/t5/Automation-articles/Setting-up-token-validation-within-Automations-using-the/ba-p/2733749#M1695].
             * MATLS support to ensure connection are trusted from Jira Cloud to on-premise CI systems and vice-versa.
             * Support for OAuth with Automation for Jira. Currently this is not supported and it would be great to have this implemented, for example with using Google APIs for Send Web Request Actions, as Google APIs only support OAuth.
             * Confirm if it's also possible to support HMAC based authentication for both inbound and outbound web requests .
            Mario Corona made changes -
            Description Original: *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|https://community.atlassian.com/t5/Automation-articles/Setting-up-token-validation-within-Automations-using-the/ba-p/2733749#M1695].
             * MATLS support to ensure connection are trusted from Jira Cloud to on-premise CI systems and vice-versa.
             * Support for OAuth with Automation for Jira. Currently this is not supported and it would be great to have this implemented, for example with using Google APIs for Send Web Request Actions, as Google APIs only support OAuth.
             * Confirm if it's also possible to support HMAC based authentication.             		New: *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 inbound and 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|https://community.atlassian.com/t5/Automation-articles/Setting-up-token-validation-within-Automations-using-the/ba-p/2733749#M1695].
             * MATLS support to ensure connection are trusted from Jira Cloud to on-premise CI systems and vice-versa.
             * Support for OAuth with Automation for Jira. Currently this is not supported and it would be great to have this implemented, for example with using Google APIs for Send Web Request Actions, as Google APIs only support OAuth.
             * Confirm if it's also possible to support HMAC based authentication for both .
            Mario Corona made changes -
            Summary Original: More authentication options for outgoing webhook "Send web request" component - e.g. to support GraphQL Actions, NTLM auth, OAuth for use with Google APIs, MATLS support, HMAC Support New: 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
            Enida made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 1017011 ]
            Michel Guedes made changes -
            Description Original: *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|https://community.atlassian.com/t5/Automation-articles/Setting-up-token-validation-within-Automations-using-the/ba-p/2733749#M1695].
             * MATLS support to ensure connection are trusted from Jira Cloud to on-premise CI systems and vice-versa.
             * Support for OAuth with Automation for Jira. Currently this is not supported and it would be great to have this implemented, for example with using Google APIs for Send Web Request Actions, as Google APIs only support OAuth.
             *  

                          		New: *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|https://community.atlassian.com/t5/Automation-articles/Setting-up-token-validation-within-Automations-using-the/ba-p/2733749#M1695].
             * MATLS support to ensure connection are trusted from Jira Cloud to on-premise CI systems and vice-versa.
             * Support for OAuth with Automation for Jira. Currently this is not supported and it would be great to have this implemented, for example with using Google APIs for Send Web Request Actions, as Google APIs only support OAuth.
             * Confirm if it's also possible to support HMAC based authentication.
            Michel Guedes made changes -
            Summary Original: More authentication options for outgoing webhook "Send web request" component - e.g. to support GraphQL Actions, NTLM auth, OAuth for use with Google APIs, MATLS support New: More authentication options for outgoing webhook "Send web request" component - e.g. to support GraphQL Actions, NTLM auth, OAuth for use with Google APIs, MATLS support, HMAC Support
            Michel Guedes made changes -
            Description Original: *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|https://community.atlassian.com/t5/Automation-articles/Setting-up-token-validation-within-Automations-using-the/ba-p/2733749#M1695].
             * MATLS support to ensure connection are trusted from Jira Cloud to on-premise CI systems and vice-versa.
             * Support for OAuth with Automation for Jira. Currently this is not supported and it would be great to have this implemented, for example with using Google APIs for Send Web Request Actions, as Google APIs only support OAuth.

                          		New: *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|https://community.atlassian.com/t5/Automation-articles/Setting-up-token-validation-within-Automations-using-the/ba-p/2733749#M1695].
             * MATLS support to ensure connection are trusted from Jira Cloud to on-premise CI systems and vice-versa.
             * Support for OAuth with Automation for Jira. Currently this is not supported and it would be great to have this implemented, for example with using Google APIs for Send Web Request Actions, as Google APIs only support OAuth.
             *  

             
            Charlie Gavey made changes -
            Link New: This issue is duplicated by AUTO-932 [ AUTO-932 ]
            Charlie Gavey made changes -
            Description Original: *Summary*

            Support for OAuth with Automation for Jira. Currently this is not supported and it would be great to have this implemented, for example with using Google APIs for Send Web Request Actions, as Google APIs only support OAuth.

                          		New: *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|https://community.atlassian.com/t5/Automation-articles/Setting-up-token-validation-within-Automations-using-the/ba-p/2733749#M1695].
             * MATLS support to ensure connection are trusted from Jira Cloud to on-premise CI systems and vice-versa.
             * Support for OAuth with Automation for Jira. Currently this is not supported and it would be great to have this implemented, for example with using Google APIs for Send Web Request Actions, as Google APIs only support OAuth.

             
            Charlie Gavey made changes -
            Summary Original: More authentication options for outgoing webhook "Send web request" component - support OAuth for use with Google APIs, MATLS support to ensure connection are trusted from Jira Cloud to on-premise CI systems and vice-versa. New: More authentication options for outgoing webhook "Send web request" component - e.g. to support GraphQL Actions, NTLM auth, OAuth for use with Google APIs, MATLS support

              dfc44bd03767 Scott Bell
              68fd6ffad335 Christian Beaulieu (Inactive)
              Votes:
              35 Vote for this issue
              Watchers:
              43 Start watching this issue

                Created:
                Updated: