<?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>article Qlik Excel Add-in OAuth Errors After Tenant Rename (OAUTH-1 and OAUTH-14) in Member Articles</title>
    <link>https://community.qlik.com/t5/Member-Articles/Qlik-Excel-Add-in-OAuth-Errors-After-Tenant-Rename-OAUTH-1-and/ta-p/2544483</link>
    <description>&lt;P class=""&gt;If your Qlik Cloud tenant hostname was recently renamed (for example, from company-old.us.qlikcloud.com to company-new.us.qlikcloud.com) and users are now receiving OAuth errors when connecting the Qlik Excel Add-in, this article explains what is happening and how to resolve it.&lt;/P&gt;&lt;P class=""&gt;&lt;FONT size="5"&gt;&lt;STRONG&gt;Symptoms&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P class=""&gt;Users open Excel, launch the Qlik Add-in, and receive one of the following errors during authentication:&lt;/P&gt;&lt;P class=""&gt;OAUTH-1: redirect_uri is not registered (Status 400)&lt;/P&gt;&lt;P class=""&gt;OAUTH-14: OAuth client is not authorized&lt;/P&gt;&lt;P class=""&gt;These errors appear even though the add-in was working before the tenant rename.&lt;/P&gt;&lt;P&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Resolution&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Log in to the Qlik Cloud Management Console on the new tenant hostname.&lt;/LI&gt;&lt;LI&gt;Go to OAuth and delete the existing OAuth client used for the Excel Add-in.&lt;/LI&gt;&lt;LI&gt;Create a new OAuth client with the following settings: Client type: Public. Grant types: Authorization Code. User default scope: Enabled. Allowed origins: your current tenant URL (e.g., &lt;A href="https://company.us.qlikcloud.com" target="_blank"&gt;https://company.us.qlikcloud.com&lt;/A&gt;).&lt;/LI&gt;&lt;LI&gt;Go to Settings &amp;gt; Sharing and reports &amp;gt; Qlik add-ins for Microsoft Office. Select the new OAuth client from the dropdown and download the updated manifest.xml file.&lt;/LI&gt;&lt;LI&gt;Distribute the new manifest.xml to your users. Users must remove the old add-in from Excel before installing the new one.&lt;/LI&gt;&lt;/OL&gt;&lt;P class=""&gt;Important: If users access the tenant through both the original URL and an alias, add both to the allowed origins field. Missing either one will cause authentication to fail.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;FONT color="#339966"&gt;Cause&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;The Excel Add-in manifest.xml and its OAuth client are created as a pair and are tied to a specific tenant hostname. When the tenant is renamed, the existing OAuth client retains the old hostname in its redirect URIs and allowed origins, triggering OAUTH-1. If the manifest is recreated but the OAuth client configuration still has incorrect settings, OAUTH-14 follows. The manifest file cannot be edited to point to a new hostname. It must be regenerated from a newly created OAuth client on the correct tenant.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Related Content&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Tabular Reporting OAUTH Error Status 400 resolution:&amp;nbsp;&lt;A href="https://community.qlik.com/t5/Official-Support-Articles/Tabular-Reporting-OAUTH-Error-Status-400-resolution/ta-p/1716773" target="_blank"&gt;https://community.qlik.com/t5/Official-Support-Articles/Tabular-Reporting-OAUTH-Error-Status-400-resolution/ta-p/1716773&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;Qlik Help: Administer the Qlik add-in for Microsoft Office:&amp;nbsp;&lt;A href="https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Admin/mc-administer-add-in.htm" target="_blank"&gt;https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_Hub/Admin/mc-administer-add-in.htm&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;</description>
    <pubDate>Tue, 10 Mar 2026 16:31:06 GMT</pubDate>
    <dc:creator>AnaSilva</dc:creator>
    <dc:date>2026-03-10T16:31:06Z</dc:date>
    <item>
      <title>Qlik Excel Add-in OAuth Errors After Tenant Rename (OAUTH-1 and OAUTH-14)</title>
      <link>https://community.qlik.com/t5/Member-Articles/Qlik-Excel-Add-in-OAuth-Errors-After-Tenant-Rename-OAUTH-1-and/ta-p/2544483</link>
      <description>&lt;P&gt;Resolve OAUTH-1 and OAUTH-14 errors on the Qlik Excel Add-in caused by a Qlik Cloud tenant hostname rename. Includes steps to recreate the OAuth client and redeploy the manifest.xml.&lt;/P&gt;</description>
      <pubDate>Tue, 10 Mar 2026 16:31:06 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Member-Articles/Qlik-Excel-Add-in-OAuth-Errors-After-Tenant-Rename-OAUTH-1-and/ta-p/2544483</guid>
      <dc:creator>AnaSilva</dc:creator>
      <dc:date>2026-03-10T16:31:06Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Excel Add-in OAuth Errors After Tenant Rename (OAUTH-1 and OAUTH-14)</title>
      <link>https://community.qlik.com/t5/Member-Articles/Qlik-Excel-Add-in-OAuth-Errors-After-Tenant-Rename-OAUTH-1-and/tac-p/2544486#M2390</link>
      <description>&lt;P&gt;Great information. Very informative!&lt;/P&gt;</description>
      <pubDate>Tue, 10 Mar 2026 16:39:01 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Member-Articles/Qlik-Excel-Add-in-OAuth-Errors-After-Tenant-Rename-OAUTH-1-and/tac-p/2544486#M2390</guid>
      <dc:creator>WeLoveQlik</dc:creator>
      <dc:date>2026-03-10T16:39:01Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Excel Add-in OAuth Errors After Tenant Rename (OAUTH-1 and OAUTH-14)</title>
      <link>https://community.qlik.com/t5/Member-Articles/Qlik-Excel-Add-in-OAuth-Errors-After-Tenant-Rename-OAUTH-1-and/tac-p/2544489#M2392</link>
      <description>&lt;P&gt;Thanks for the update—this explains the Excel Add-in error noticed.&lt;/P&gt;</description>
      <pubDate>Tue, 10 Mar 2026 17:12:43 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Member-Articles/Qlik-Excel-Add-in-OAuth-Errors-After-Tenant-Rename-OAUTH-1-and/tac-p/2544489#M2392</guid>
      <dc:creator>jeffreyfairchild</dc:creator>
      <dc:date>2026-03-10T17:12:43Z</dc:date>
    </item>
  </channel>
</rss>

