-
Suggestion
-
Resolution: Unresolved
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 .
- is duplicated by
-
- Closed
-
- Closed
-
- Closed
[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
Or company uses Google for daily operations. We also use Service Desk to track user requests such as onboarding, terminations, personnel info changes, etc. A use case for us would be:
- In Service Desk, receive an onboarding request for new hire (new hire needs Google account created for email, Drive, etc)
- Have manually triggered automation built that uses sequential web requests to:
- Perform Oauth2 API calls with Google to get authorization code
- Perform Oauth2 API calls with Google to exchange authorization code for access token
- Using access token, perform API calls with Google to create new user in Google
- Automation is then triggered manually within the onboarding ticket
This use case could be applied to numerous other Google operations we receive Service Desk requests for. Having this functionality would truly revolutionize our use Service Desk.
One of the drawback of automation for Jira is the ability to call out to other systems. We need more tools to create responsive, dynamic workflows that assist organizations in scaling, reducing technical debt, and improving efficiency.
Automation for Jira has such potential, please don't let it wither on the vine!
I have been trying to use automations to create an MS Teams channel.
I can use MS Graph explorer easily to do this but it requires an access token. There is currently no way for Jira to do the same, so we cannot currently achieve our goal.