<?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 ExtremeCloud IQ API – GET /users returns 403 for top-level admin token in ExtremeCloud IQ</title>
    <link>https://community.extremenetworks.com/t5/extremecloud-iq/extremecloud-iq-api-get-users-returns-403-for-top-level-admin/m-p/123027#M4869</link>
    <description>&lt;P&gt;I tested with Swagger on the same XIQ account (EKNOW-OFFICE, APAC_Tokyo):&lt;/P&gt;&lt;P&gt;- Bearer token from POST /login (Administrator): GET /users -&amp;gt; 200 OK (7 users)&lt;BR /&gt;- API token (generated from Global Settings &amp;gt; API Token Management by the same top-level Administrator): GET /users -&amp;gt; 403 Forbidden&lt;BR /&gt;(the same API token returns 200 for GET /users/me and GET /users/external,&lt;BR /&gt;and it includes all permissions listed by GET /auth/permissions, including rmuser-list / account-user-list)&lt;/P&gt;&lt;P&gt;So GET /users fails only with the API token, not with the login token.&lt;BR /&gt;Could you confirm:&lt;BR /&gt;1. Is GET /users restricted for API tokens by design?&lt;BR /&gt;2. If not, which permission (or token setting) is required for an API token to call GET /users?&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
    <pubDate>Wed, 18 Nov 2026 09:32:42 GMT</pubDate>
    <dc:creator>KD</dc:creator>
    <dc:date>2026-11-18T09:32:42Z</dc:date>
    <item>
      <title>ExtremeCloud IQ API – GET /users returns 403 for top-level admin token</title>
      <link>https://community.extremenetworks.com/t5/extremecloud-iq/extremecloud-iq-api-get-users-returns-403-for-top-level-admin/m-p/123027#M4869</link>
      <description>&lt;P&gt;I tested with Swagger on the same XIQ account (EKNOW-OFFICE, APAC_Tokyo):&lt;/P&gt;&lt;P&gt;- Bearer token from POST /login (Administrator): GET /users -&amp;gt; 200 OK (7 users)&lt;BR /&gt;- API token (generated from Global Settings &amp;gt; API Token Management by the same top-level Administrator): GET /users -&amp;gt; 403 Forbidden&lt;BR /&gt;(the same API token returns 200 for GET /users/me and GET /users/external,&lt;BR /&gt;and it includes all permissions listed by GET /auth/permissions, including rmuser-list / account-user-list)&lt;/P&gt;&lt;P&gt;So GET /users fails only with the API token, not with the login token.&lt;BR /&gt;Could you confirm:&lt;BR /&gt;1. Is GET /users restricted for API tokens by design?&lt;BR /&gt;2. If not, which permission (or token setting) is required for an API token to call GET /users?&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Wed, 18 Nov 2026 09:32:42 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecloud-iq/extremecloud-iq-api-get-users-returns-403-for-top-level-admin/m-p/123027#M4869</guid>
      <dc:creator>KD</dc:creator>
      <dc:date>2026-11-18T09:32:42Z</dc:date>
    </item>
  </channel>
</rss>

