Qlik Sense SaaS Rest-Connector HTTP Redirect problem

[williamandersson]

Hi!

I am trying to connect to the Spotify API per this guide here: https://developer.spotify.com/documentation/general/guides/authorization/code-flow/

This requires you to authorize via a redirect uri. When I am trying to come up with a solution in Qlik for this, I get the error message "HTTP response contains a redirect. Redirects are not allowed in Qlik Cloud."

Is there a solution to this? Or have anyone stumbled upon this aswell that have figured out a way to get to the redirect?

Thanks!

[Frank_S · Accepted solution]

Hi 

Try open DEV TOOLS, reproduce the issue and create/save a HAR file

Check the HAR file for noticeable redirection url's (perhaps linked to a VPN or other Cloud based security tools in your network).

Also check this:
Creating a new identity provider configuration

11. At your identity provider, allow list your tenant URL. The setting has different names, for example, Allowed Callback URLs, Redirect URI, or Login redirect URI.
 

Kind regards...

[williamandersson]

Thank you Frank, will try your tip!

[Frank_S]

No worries!

[Frank_S]

Did it work? @williamandersson?

Or at the very least, did the HAR file give any clues?

[abubakarseo22]

I understand the issue you're facing. Qlik Cloud does not allow redirects in HTTP responses, which is necessary for the Spotify API authorization process using the Authorization Code Flow.

To work around this limitation, you can try the following approach:

1. Use Implicit Grant Flow (if applicable): Instead of Authorization Code Flow, consider using Implicit Grant Flow if Spotify supports it for your use case. Implicit Grant Flow does not involve server-side redirects and may be more suitable for environments like Qlik Cloud.

2. Local Proxy Server: Set up a local proxy server on your machine or on a server where redirects are allowed. Your Qlik application can then send requests to this proxy server, which in turn manages the Spotify API authorization flow, including handling redirects.

3. Manual Authorization: If possible within your workflow, manually authorize your application through the Spotify website or another interface that supports redirects. Once authorized, use the obtained tokens directly in your Qlik application without needing to handle redirects during runtime.

These alternatives should help you navigate around the redirect limitation in Qlik Cloud while still enabling integration with the Spotify API. If you need further assistance with implementation details or have specific requirements, feel free to ask.