Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Meet Qlik's New CEO. The Future Is Bright — Here's What to Expect
Sonja_Bauernfeind
Digital Support
Digital Support

Hello Qlik admins and developers,

Previously, the Dropbox API used only long-lived access tokens. These long-lived access tokens have been deprecated since the fall of 2022, and only short-lived access tokens are created. Long-lived tokens remain usable for existing authentications.

The Qlik Dropbox connectors have maintained the use of long-lived access tokens, and it is now time to deprecate these tokens and remove them. We aim to end support for long-lived tokens by October 31, 2025.

What action do I need to take?

Re-authenticate to avoid interruption.

You will not have to take action for connection definitions created in Qlik products released from 2023 and onwards, and which were created or re-authenticated after 2022.

This is applicable to the following scenarios:

  • Qlik Sense: Client Managed and Qlik Cloud
    • Dropbox file location connector
    • Dropbox Metadata connector
  • Qlik Web Connector Standalone
    • Qlik Dropbox Connector

If you are using a long-lived access token in a Dropbox connection definition, you must follow the steps below to re-authenticate. This can be done proactively at any time, which will avoid the connections from breaking.

What if I do not re-authenticate in time?

Your connections will stop working once the long-lived access token expires. You can still re-authenticate in the same way at a later time; your connection will be repaired, and your reloads will work again.

Is there some way for me to identify the connections?

Unfortunately, there is no indication showing which type of token is used. However, if you are not sure when the connection was created or last re-authenticated, there is no harm in re-authenticating, regardless of whether it is necessary or not. 

How to re-authenticate in Qlik Sense: Client Managed and Qlik Cloud

To re-authenticate the Dropbox connectors in Qlik Sense, update the connection within the Data load editor, then select Authenticate and follow the on-screen process to retrieve a new Authentication Code. Verify and Save the connection when done.

How to re-authenticate the Qlik Web Connector: Standalone

Re-authenticate via the CanAuthenticate table by selecting to Clear the current Authentication Token, and then Authenticate to get a new Authentication Token. Save and Run when done.

Additional recommendations

While performing this review of your Dropbox connection definitions, it may also be an opportunity to remove any redundant connection definitions not in use.

 

If you have any questions, we're happy to assist. Reply to this blog post or start a chat with us.

 

Thank you for choosing Qlik,
Qlik Support

1 Comment