The current documentation advises configuring the connection with the following setup: export const SISENSE_CONTEXT_CONFIG: SisenseContextConfig = { url: '<instance url>', // replace with the URL of your Sisense instance token: '<api token>', // replace with the API token of your user account }; This approach involves passing the API token directly from the frontend, which raises security concerns. Can someone please recommend a more secure method for establishing the...

hi herajapakse You shouldn't use API Tokens like this in production, for the reasons you state. We're going to update our docs soon to reflect this more strongly.Most customers use Single Sign On (sso) for embedded use cases, and the Sisense platform has built in support for this (not specific to Compose SDK, but holistically). If SSO is configured for Sisense, then your Compose SDK configuration is pretty simple, just set ssoEnabled = true as documented here https://sisense.dev/g...

Help with connecting to Sisense instance | Help and How-To

MoreDiscussions

Help with connecting to Sisense instance | Help and How-To | Sisense Community