Implementing web token access in spring boot
In this i tried to implement to render i-frame without login . Below i've attached my backend code for jwt token generation too. @Service public class SisenseTokenService { // Use the Shared Secret from your Sisense Admin panel private static final String SHARED_SECRET = "MY_secret_key"; public static String generateSisenseJWT(String userEmail) { long nowEpoch = Instant.now().getEpochSecond(); return Jwts.builder() .claim("sub", userEmail) // Sisense user email .claim("iat", nowEpoch) // Issued At .claim("jti", UUID.randomUUID().toString()) // Unique token ID .signWith(SignatureAlgorithm.HS256, SHARED_SECRET.getBytes(StandardCharsets.UTF_8)) .compact(); } } output for token: token:e decoded: { "sub": "[email protected]", "tenantId": "system", "iat": , "jti": "" } in frontend - <iframe src={`https://sisense-dev.cscs-apps.com/app/main/dashboards/686bca7cef95f60033490c63?embed=true&web_access_token=e`} width="100%" height="100%" /> still it is not working why? kindly help asap, it is an important blockerSolved43Views0likes4CommentsHow to prevent iframe reload when switching tabs in React app embedding Sisense dashboard?
Hi everyone, I'm embedding a Sisense dashboard using an iframe inside a React-based platform. The iframe is rendered on a dedicated Insights tab route: insights. Every time I switch away from this tab and return to it, the iframe reloads, which causes unnecessary load time and loss of dashboard state (like applied filters or selections). My goal is to mount the iframe only once, keep it cached in memory, and just hide/show it based on tab switching, without triggering a reload. Here’s what I’m trying to achieve: Mount the Sisense iframe only once (on first visit to /insights) Persist it in memory even when navigating away Show it again without reloading when coming back Has anyone implemented this pattern or has best practices around iframe caching or persistent embedding of dashboards in a React environment? Would love to hear suggestions or recommended approaches from the community! Thanks!79Views0likes5CommentsHow to capture clicked metric value from a Pie Chart using Compose SDK?
Hi everyone, I'm embedding a Sisense dashboard using the Compose SDK (@sisense/sdk-ui) in my React app. I can render widgets using WidgetById and everything looks fine visually. What I'm trying to do now is capture user interaction with a Pie Chart — specifically, I want to know which pie slice the user clicked, such as the category name ("Active", "Closed", etc.). Here’s what I’ve tried so far: Added onWidgetClick and container onClick event handlers Used event.detail, event.target, etc. Tried a custom double-click workaround with setTimeout Checked the widget configuration for drill options and filters But none of these gave me the value or label of the clicked pie slice. The click event doesn't contain the metric/dimension value. Context: Using Compose SDK (@sisense/sdk-ui) Rendering widgets from dashboard via /api/v1/dashboards/:id/widgets Widget type: Pie Chart Rendering via WidgetById inside SisenseContextProvider What I need: Is it possible to get the clicked dimension or category from a pie chart using Compose SDK? If not, is there a workaround via classic embedding or JavaScript SDK? Any configuration or drill setup that enables this behavior? Thanks in advance for any guidance or examples. Would really appreciate help from someone who’s tackled this before!Solved53Views0likes3CommentsImplementing Simply Ask in Sisense Embedded Dashboard - A Technical Investigation
Has anyone successfully implemented Simply Ask in an embedded dashboard using the Embed SDK? Are there specific configuration requirements or permissions that need to be set? Is there a recommended approach between using iFrame, SisenseJS, or the Embed SDK for implementing Simply Ask?264Views0likes2CommentsAllow multiselect
When designing a dashboard, we want to disable multi-select for a specific filter so that end users can only select one value. The challenge is that we can’t preselect a single value during dashboard creation, since the valid values vary from user to user. Preselecting a value might result in - That value not being available for certain users. Confusion for end users if they see a value that doesn’t apply to them. Ideally, we want the filter to force the user to choose a single value from their applicable options, without allowing multiple selections and without preselecting any default value.41Views0likes0CommentsLeveling up analytics: From home-grown solution to Sisense
BigTinCan, a SaaS-based enterprise sales enablement solution developed by a small team in Minneapolis, originally used an in-house developed data visualization system. This system was based on popular open-source graphing libraries and initially met the needs of their customers. However, as the demand for more features such as additional dashboards, reports, automatic subscriptions, and filters grew, the engineering team found itself overwhelmed. The diverse needs of their customers created a never-ending roadmap of feature requests, prompting the team to evaluate commercially available data visualization products.2KViews2likes0Comments