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

Announcements
Qlik and ServiceNow Partner to Bring Trusted Enterprise Context into AI-Powered Workflows. Learn More!
cancel
Showing results for 
Search instead for 
Did you mean: 
loki20beta
Partner - Contributor II
Partner - Contributor II

authorization issues in our tennant

We are trying to access the tenant we have and we don't use it often. Today I got this when navigating to tennant address. Instead of https://TENNANT-address.us.qlikcloud.com/ it send to https://dev-l1cbldpnpskjgnb8.us.auth0.com/u/login?state=hKF. . Did Qlik accidentally used dev keys? Did is happen only to us or someone else?

PS: it wasn't qlik, it was us

Labels (2)
1 Solution

Accepted Solutions
NickGogin
Contributor
Contributor

Check if a custom Identity Provider was added. You can verify this in Administration → Identity Provider.

A common reason for having a custom Identity Provider is the use of the qlik-embed framework to integrate Qlik objects into external web applications.

More details on why Identity Providers are needed in that context can be found here:
Qlik Embed Web Component Quick Start

If you no longer need the active third-party Identity Provider, you can simply deactivate it — the default authentication flow will be restored automatically.

View solution in original post

2 Replies
NickGogin
Contributor
Contributor

Check if a custom Identity Provider was added. You can verify this in Administration → Identity Provider.

A common reason for having a custom Identity Provider is the use of the qlik-embed framework to integrate Qlik objects into external web applications.

More details on why Identity Providers are needed in that context can be found here:
Qlik Embed Web Component Quick Start

If you no longer need the active third-party Identity Provider, you can simply deactivate it — the default authentication flow will be restored automatically.

loki20beta
Partner - Contributor II
Partner - Contributor II
Author

That was it, thank you!