Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
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.
Symptoms
Users open Excel, launch the Qlik Add-in, and receive one of the following errors during authentication:
OAUTH-1: redirect_uri is not registered (Status 400)
OAUTH-14: OAuth client is not authorized
These errors appear even though the add-in was working before the tenant rename.
Resolution
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.
Cause
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.
Related Content