GitHub user victormaneac added a comment to the discussion: Superset embed dashboard with JWT
In short, they are the same, but one is the main application's access token and the other is the Superset's access token. In the context of the question, an access token is what the UI hosted app is retrieving when authenticating the user with their own identity system. The guest token is the same thing, but on the downstream, more precisely, it is the access token that Superset returns when a pre-defined user, with the required rights, requests a guest token. Putting it all together: 1. You log in to the UI hosted app, and you receive an access token 2. Some minutes after, you navigate to a section that displays the embedded dashboard from Superset. For the page to load, the UI hosted app will make a call to another internal application (that you need to build and deploy) that will a. authenticate to Superset with a pre-defined user, having the required rights b. call /guest-token API to generate an access token for accessing Superset c. return the guest token to the caller 3. UI hosted app loads the Dashboard by embedding the iframe and attaching the guest token retrieved above GitHub link: https://github.com/apache/superset/discussions/31288#discussioncomment-14308784 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
