<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Jira Service management connector does not support Atlassian Service Account scoped API tokens in Workato Pros Discussion Board</title>
    <link>https://systematic.workato.com/t5/workato-pros-discussion-board/jira-service-management-connector-does-not-support-atlassian/m-p/12228#M4690</link>
    <description>&lt;P&gt;We migrated our Atlassian integrations to the new Atlassian Service Accounts.&lt;/P&gt;&lt;P&gt;Connection using API token succeeds in Workato JSM connector, but all JSM actions return 401 Unauthorized.&lt;/P&gt;&lt;P&gt;The same credentials work successfully when calling Atlassian APIs directly through:&lt;/P&gt;&lt;P&gt;&lt;A href="https://api.atlassian.com/ex/jira/%7BcloudId%7D/" target="_blank"&gt;https://api.atlassian.com/ex/jira/{cloudId}/&lt;/A&gt;...&lt;/P&gt;&lt;P&gt;using Bearer authentication.&lt;/P&gt;&lt;P&gt;It seems the native Jira Service Desk connector still uses the legacy site-based authentication flow instead of Atlassian’s scoped token API gateway flow required for Service Accounts.&lt;/P&gt;&lt;P&gt;Can Workato confirm whether Jira Service Desk connector officially supports Atlassian Service Account scoped API tokens?&lt;/P&gt;&lt;P&gt;If not, is support planned on the roadmap?&lt;/P&gt;</description>
    <pubDate>Mon, 18 May 2026 08:47:17 GMT</pubDate>
    <dc:creator>omri_avigdor</dc:creator>
    <dc:date>2026-05-18T08:47:17Z</dc:date>
    <item>
      <title>Jira Service management connector does not support Atlassian Service Account scoped API tokens</title>
      <link>https://systematic.workato.com/t5/workato-pros-discussion-board/jira-service-management-connector-does-not-support-atlassian/m-p/12228#M4690</link>
      <description>&lt;P&gt;We migrated our Atlassian integrations to the new Atlassian Service Accounts.&lt;/P&gt;&lt;P&gt;Connection using API token succeeds in Workato JSM connector, but all JSM actions return 401 Unauthorized.&lt;/P&gt;&lt;P&gt;The same credentials work successfully when calling Atlassian APIs directly through:&lt;/P&gt;&lt;P&gt;&lt;A href="https://api.atlassian.com/ex/jira/%7BcloudId%7D/" target="_blank"&gt;https://api.atlassian.com/ex/jira/{cloudId}/&lt;/A&gt;...&lt;/P&gt;&lt;P&gt;using Bearer authentication.&lt;/P&gt;&lt;P&gt;It seems the native Jira Service Desk connector still uses the legacy site-based authentication flow instead of Atlassian’s scoped token API gateway flow required for Service Accounts.&lt;/P&gt;&lt;P&gt;Can Workato confirm whether Jira Service Desk connector officially supports Atlassian Service Account scoped API tokens?&lt;/P&gt;&lt;P&gt;If not, is support planned on the roadmap?&lt;/P&gt;</description>
      <pubDate>Mon, 18 May 2026 08:47:17 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/workato-pros-discussion-board/jira-service-management-connector-does-not-support-atlassian/m-p/12228#M4690</guid>
      <dc:creator>omri_avigdor</dc:creator>
      <dc:date>2026-05-18T08:47:17Z</dc:date>
    </item>
  </channel>
</rss>

