NOTE: SaaS discovery is only supported via OAuth 2.0. The Inline Credentials (Basic Auth) Authentication mechanism can still be used but only for Orchestration actions via the workflows. Atlassian Jira OAUTH 2.0 does not support Create/ Delete User orchestration actions. If you want to create and delete users via the Workflows, please create an additional config using the Inline Credentials (Basic Auth) Authentication mechanism. Authentication mechanism For OAuth 2.0 (3LO) To generate Client ID and Client secret, and set the scopes, refer Atlassian documentation: https://developer.atlassian.com/cloud/jira/platform/oauth-2-3lo-apps/#enabling-oauth-2-0--3lo- Authorization Scopes to be Set Up In Granular scopes, select the following scopes. For more details: https://developer.atlassian.com/cloud/jira/platform/scopes-for-oauth-2-3LO-and-forge-apps/ Discovery Scopes: - read:jira-user - read:user:jira - read:audit-log:jira - read:jira-work - read:license:jira - read:group:jira - read:issue:jira - read:audit-log:jira - offline_access Orchestration Scopes: - manage:jira-project - manage:jira-configuration - Write:jira-work - manage:jira-data-provider - offline_access - write:group:jira For Basic Auth App Installation Parameters: a. Jira Account URL (It is the Jira account URL. eg: example.atlassian.net) b. Email (It is the Jira admin account email.) c. Api Token (Create an API token from your Atlassian account) - Log in to https://id.atlassian.com/manage/api-tokens. - Click Create API token. - From the dialog that appears, enter a memorable and concise Label for your token and click Create. - Click Copy to clipboard, then paste the token to your script, or elsewhere to save Additional Parameters required for Freshservice related actions d. Freshservice Domain e. Freshservice Api key View detailed instructions to set up the integration here: https://support.freshservice.com/support/solutions/articles/50000003500