Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to embed superset dashboard in an iframe from an angular application #15737

Closed
HariniPuppala opened this issue Jul 16, 2021 · 3 comments
Closed
Labels
question & help wanted Use Github discussions instead

Comments

@HariniPuppala
Copy link

Hi,
I am trying to integrate superset dashboard into an angular based web application by embedding superset dashboard in an iframe.
I did the following setup:
Configured LDAP Authentication in superset.
Enabled a Custom Security Manager to authenticate based on a jwt-token. The jwt-token is decoded and the credentials are validated as per the configured LDAP settings in the Custom Security manager.
The jwt-token based authentication is working as expected and I am able to redirect to the dashboards without the login page. But, the same is not working when passed in an iframe.

Getting the below error in iframe:
MicrosoftTeams-image

There is this warning message in superset log:
WARNING:root:Class 'werkzeug.local.LocalProxy' is not mapped

Can anyone please help on this. Thanks in advance!

@junlincc junlincc added the question & help wanted Use Github discussions instead label Jul 16, 2021
@ghost
Copy link

ghost commented Jul 20, 2021

I am also getting the same error after upgrading superset from 1.1.0. to 1.2.0
Does anyone know about this error.

@gokultrivandrum
Copy link

@HariniPuppala @srikark16 Any solution for the error, Also other than iFrame is there any client JS for integrating Dashboard ? @junlincc

@jhult
Copy link
Contributor

jhult commented Sep 17, 2021

Also related to #16718.

@apache apache locked and limited conversation to collaborators Feb 2, 2022
@geido geido converted this issue into discussion #18313 Feb 2, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
question & help wanted Use Github discussions instead
Projects
None yet
Development

No branches or pull requests

4 participants