Setting Up SSO SAML 2.0 with G Suite
G Suite is a package of cloud-based services that can provide your company or school with a whole new way to work together online—not just using email and chat, but over video conferences, social media, real-time document collaborations, and more. Users can use their G Suite credentials to sign in to enterprise cloud applications via Single Sign-On (SSO). An identity and access management (IAM) service provides administrators with a single place to manage all users and cloud applications. You don't have to manage individual user IDs and passwords tied to individual cloud applications for each of your users. An IAM service provides your users with a unified sign-on across all their enterprise cloud applications. This page describes how to add Sisense to G Suite and configure SSO-support with SAML 2.0. Note: This page reflects a 3rd party’s application which may change. If the steps described here do not match what you see in your G Suite account, you can use the generic Sisense SAML documentation, along with the IdP’s documentation. Connecting Sisense to G Suite Log in to your admin.google.com account with your G Suite account Select Apps on the main page Select SAML apps Step 1 Create a new application. “+” button or “ SETUP MY OWN CUSTOM APP” Step 2 Download Certificate or IDP Metadata, save SSO URL. Use notepad to open certificate or Metadata file, save lines starting from -----BEGIN CERTIFICATE----- to -----END CERTIFICATE----- This information will be used for Sisense SAML configuration. Step 3 Enter Application Name - Sisense Step 4 Enter ACS URL - https://yourSisensedomain.com/api/v1/authentication/login_saml_callback/ Entity ID - Sisense Enable Signed Response, select Name ID Format Step 5 Add new mapping for User.email Click Finish. And Ok in the popup window. Enable Sisense application for All users In the Sisense SSO page add Remote Login URL - saved from the Step 2 and Certificate Click Save. Users who access any of the web pages on your Sisense server, will be redirected to Google G Suite authentication Was this article helpful?Setting Up SSO SAML 2.0 with Okta
Okta provides secure identity management and single sign-on to applications that you can add to your Okta account. From Okta, you and your users can log in to Okta and then access applications such as Sisense without having to log in to each application. Okta supports applications that support SAML 2.0, such as Sisense. This page describes how to add Sisense to Okta and configure SSO-support with SAML 2.0. Note: This page reflects a 3rd party’s application which may change. If the steps described here do not match what you see in your Okta account, you can use the generic Sisense SAML documentation, along with the IdP’s documentation. Adding Sisense to Okta To add Sisense to Okta: Log in to Okta. In the menu bar, click Applications -> Browse App Catalog. In the Search field enter Sisense and choose Sisense SAML app. Then click Add Integration. Put Sisense application URL in Base URL and press Done. Sisense is added to your Apps. After you configure SAML 2.0 for Sisense, you can click this application in Okta to launch your Sisense dashboard. Configuring SAML 2.0 for Sisense To configure SAML 2.0: Under the Applications tab, select Applications. In the Applications page, click Sisense. In the Sisense app menu bar, click the Sign On tab -> Edit. Okta’s setup instructions are expanded. Click More Details to get your SSO information which Sisense needs to configure SSO. From the Okta setup instructions, copy the Remote Login URL, Remote Logout URL, and Download Signing Certificate. In the Sisense Web Application, select Single Sign On under the Admin tab. In the Single Sign On page, activate SSO. In the Remote Login URL, Remote Logout URL, and Public X-509 Certificate fields, enter your Okta SSO details into the relevant fields described in Step 4 of this procedure. Click Save. The Okta users you assigned to the Sisense application can access Sisense through Okta without having to log in to Sisense directly.
Who's doing multitenancy?!
Referencing this table of tenant segregation levels, we have been doing the Internal Capabilities approach for 8 years (user groups and JWT with our own SSO router which predates the one in the marketplace). We recently migrated from Windows to Linux and would like to find a way for our staff to manage the Sisense environment via SSO using Entra ID. We're building an intermediate solution but are also considering Sisense Tenants. We assume, without having done a POC, that we'll be able to configure the system tenant to use Entra, while configuring the tenants to use the JWT we're currently using. We are drawn to allowing our clients to use the All Dashboards feature within their tenant. We will supress their access to White Labelling and SSO. We use Live Models, not Elasticubes. We expect some positive feedback on clients having some access to review their data models as well. We realize that we have to migrate our clients into the Sisense Tenants if we go that route. My question for YOU then... If you use Sisense Tenants, how's it going? What's your scenario and how has this feature supported you? Has it let you down in any way? If you don't use Sisense Tenants, why not? Is there something to your multitenancy that Tenants doesn't support (e.g. Report Manager)? Any other thoughts, advice or feedback... things I should consider and questions I should be asking? Thanks in advance!Script to retrieve the user list with first name and last, email, and userID
By following these instructions, users can efficiently check and download a CSV file containing the list of users meeting specific criteria from the developer console in their preferred browser under the user with Admin rights.
