SAML Authentication is only available on 'On-Premise' Offers
If you coordinate your companies authentication over a SAML provider such as Okta or Google GSuite SAML, you can easily integrate and start using right away. The following documentation is organized for integrating Google GSuite SAML App. However, the same principles apply for any SAML2 provider such as Okta.
Check that your rakam-bi container has the following environment variables available;
Should point to your load balancers A/CNAME. You may verify this using the shell command:
5h (the default value)
Time to live of a cookie acquired via SAML login.
- Optional variable
Navigate to your SAML Apps at your GSuite admin console. Select 'SETUP MY OWN CUSTOM APP'
Click on 'Download' button and save the XML file.
You can choose any name for this SAML App, description and logo are optional.
Enter the following URL's of your Rakam-BI deployment.
- ACS URL:
- Entity ID:
Click to 'Edit Service' and under 'Service Status' section toggle
ON for everyone
If you which to map your user's first and last names to rakam-bi, navigate to 'Attribute Mapping' and map the following fields. By default, users with SAML authentication are not able to create projects. If you choose to disable this, you can add a static mapping from
Log in with your administrator account (the first account you registered to your rakam-bi deployment.) .Navigate to your administration page on rakam-bi (htttps://your-rakam-bi-url.com/admin/auth). Select the SAML section and paste your Idp metadata XML contents.
You can verify the installation via logging out and locating 'Connect via SAML' button. Once this integration enabled, registration of local accounts is not possible. Although already registered users will be able to log in over 'Use a Local User' option.
Once a local user is logged in using SAML, it is not possible to log in using local credentials anymore but the administrator user
Updated almost 3 years ago