To stay on top of their game, modern companies use a variety of software tools (like Kanbanize!) to help them work better and more efficiently. However, as the number of tools increases, so do the passwords every user has to remember as well as the load on system administrators and IT have to support. A remedy for this is Single Sign-On (SSO) – a technology which allows a company to maintain a centralized Identity Provider server that all other tools communicate with in order to authenticate and authorize users. SAML (Security Assertion Markup Language) is the most wide-spread SSO standard in the enterprise world. This is why product update 5.7 of Kanbanize provides you with the ability to integrate with your company’s SAML 2.0 Identity Provider and eliminate the need of remembering all of those passwords!

*The rest of this article assumes that you are the administrator of your Kanbanize account, have proper permissions to modify settings in your Identity Provider and are familiar with the SAML 2.0 protocol.

Here are the steps required to connect Kanbanize with your Identity Provider (IdP):

  1. In Kanbanize, open the Administration panel and go to Integrations.
  2. There, you will find a section called Single Sign-On.
  3. Tick the checkbox at the top to enable to configuration fields.
  4. In the first field, you need to enter the Entity Id of your Identity Provider. Consult the documentation and/or metadata of your IdP if you don’t know it.
  5. The second field is IdP Login Endpoint. Here, you should enter the URL to which Kanbanize should redirect login requests.
  6. Similarly, Idp Logout Endpoint is the URL to which Kanbanize should redirect logout requests. This is an optional field which means that you need to fill it in only if you want to enable Single Log-Out, too. What this means is that when users log out from Kanbanize they will be logged out of your IdP (and all other tools connected with it). Vice-versa – when users log out from your IdP they will be logged out of Kanbanize, too.
  7. In the last field, paste (without the start and end markers) the X.509 certificate that your IdP uses to sign data.
  8. The first from the fields on the right is Attribute name for Email. Here, you need to enter the name of the attribute that holds the user’s email in the authentication statement that the IdP will send to Kanbanize. If you don’t know that, consult your IdP’s documentation and/or settings.
  9. The next two fields are optional. They represent the names of the attributes that hold the user’s first and last name. This information is utilized when a user logs in for the first time in Kanbanize. An account is automatically provisioned for that user and, if the above-mentioned attributes are present, the user’s name will be filled in the account.
  10. Click Save Settings, with which the configuration of SAML in Kanbanize is complete.sso1

*Click on image to enlarge.

Now you need to set up the Identity Provider. The steps will differ for every particular IdP so, once more, you will need to consult its documentation. Here is the information that you will need:

  1. The Entity Id of Kanbanize is https://<subdomain> (replace <subdomain> with your company’s custom Kanbanize subdomain, e.g. )
  2. Assertion Consumer Service (ACS) endpoint (or the URL where the IdP will redirect after successfully authenticating and authorizing the user) is https://<subdomain>
  3. Single Logout Service (SLS) endpoint is https://<subdomain>
  4. RelayState is /ctrl_login/finish_saml_login

If your IdP supports configuration with metadata you can find it at: https://<subdomain>

When the configuration has been completed, the users that you have provisioned to use Kanbanize will be redirected to your IdP’s login page when they try to log in. Upon successful authentication and authorization, they will be redirected back to Kanbanize and live happily with one less password in their lives!

These were the general steps for configuring SAML with any Identity Provider. Below, you can find the specific step-by-step tutorials for enabling SSO with Azure Active Directory, OneLogin, and Okta as your IdP:

Configure single sign-on with Azure Active Directory
Configure single sign-on with OneLogin
Configure single sign-on with Okta

If you have any trouble don’t hesitate to contact us at

Also, let us know if this post can be improved to be more helpful!

Join our Lean Community!

We publish a new article every week. Get the latest content straight into your inbox!

2 thoughts on “Configuring SAML Single Sign-On in Kanbanize

    1. Alex Novkov

      Hi Holger,
      G Suite supports SAML 2.0 SSO so yes, it is compatible with our SSO implementation.


Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.