This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Cookie Policy. Click Preferences to customize your cookie settings.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results forย
- Community
- Forums
- Software Developers
- Re: Embed sdk was disabled due to inability to fin...
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
โ09-13-2023 11:07 PM
Hi,
Embedding Sisense dashboard using Embed SDK lib we noticed this warning on the dev tools console:
"Embed sdk was disabled due to inability to find origin of the webpage"
Our dashboard is rendering correctly and Embed SDK is used.
Anyone experienced the same warning or know the origin of this alert?
Thanks
1 ACCEPTED SOLUTION
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
โ09-14-2023 09:08 AM - edited โ09-14-2023 09:09 AM
Hi Andrea,
This usually happens due to a wrong redirection during the SSO flow. If you use the JWT handler, please ensure you handle the return_to correctly - the URL parameters should include host and cid parameters for Sisense to identify that the Sisense is rendered in a frame. Check here for more details about handling JWT return_to: https://sisense.dev/guides/accessSecurity/jwt/#step-5-joining-it-all-together
If this is not working for you, feel free to contact Sisense Support by creating a ticket in the Portal: https://community.sisense.com/t5/support-portal/bd-p/SupportPortal
Taras Skvarko
Technical Consultant
Technical Consultant
1 REPLY 1
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
โ09-14-2023 09:08 AM - edited โ09-14-2023 09:09 AM
Hi Andrea,
This usually happens due to a wrong redirection during the SSO flow. If you use the JWT handler, please ensure you handle the return_to correctly - the URL parameters should include host and cid parameters for Sisense to identify that the Sisense is rendered in a frame. Check here for more details about handling JWT return_to: https://sisense.dev/guides/accessSecurity/jwt/#step-5-joining-it-all-together
If this is not working for you, feel free to contact Sisense Support by creating a ticket in the Portal: https://community.sisense.com/t5/support-portal/bd-p/SupportPortal
Taras Skvarko
Technical Consultant
Technical Consultant
Community Toolbox
Recommended quick links to assist you in optimizing your community experience:
- Community FAQs
- Community Welcome & Guidelines
- Discussion Posting Tips
- Partner Guidelines
- Profile Settings
- Ranks & Badges
Developers Group:
Product Feedback Forum:
Need additional support?:
The Legal Stuff
Have a question about the Sisense Community?
Email [email protected]
