Single Sign-On (SSO) is a mechanism that allows a system to authenticate users and subsequently tell Sisense that the user has been authenticated. The user is then allowed to access Sisense without being prompted to enter separate login credentials.
The SSO security mechanism allows Sisense to trust the login requests it gets from your corporate authentication system, and grant access to the users that have been authenticated by it. An SSO session begins when the authenticated user requests a secured resource from Sisense while logged into your site or application. The user’s browser sends an HTTP request to Sisense that includes a cookie which contains session and authentication information. This information is then used for session validation.
Users who already have Sisense accounts can continue to access Sisense through the Sisense Login page with their current accounts. To prevent users from directly logging in to Sisense instead of your login page, your Sisense administrator can change the passwords of your current users forcing them to log in with your company’s credentials in your company’s login page.
Sisense recommends that administrators always keep a Sisense password, so that the administrator can access Sisense in case the SSO server is not available.
Sisense SSO supports two SSO protocols for securing the exchange of user authentication data , JSON Web Token (JWT) and SSO via SAML 2.0 (Security Assertion Markup Language). For more information, see SSO via JWT or SSO via SAML 2.0.
Hey! Was this article helpful?
Questions? Ask the community.