Active Directory - SAML

Add Ebbot to your Active Directory

When a user logs into Ebbot it is done using the access management platform Keycloak. Keycloak can connect to your external Active Directory (AD) using a feature called “User Federation”. This feature makes it possible to synchronise users, groups and their roles from AD to Keycloak.

We (Ebbot) always recommend that you configure the integration of Ebbot into a test AD, if you have one. If your organisation does not have a test AD, just follow the instructions and configure the integration to production.

Prerequisites in Ebbot

If you have a contact person at Ebbot that is involved in the configuration, please add this person to your AD so that they can test the login.


Provide us with IdP SAML entity descriptor metadata (URL from where it can be fetched or as a file). The URL can look something like this: "".

The federation file should include the needed attributes logging into Ebbot via AD. You will find the essential attributes below:



First name

The user’s first name

Last name

The user’s last name


The user’s email address


The user’s user ID


The role that the user should have in Ebbot


The bots that the user should access in Ebbot


The skills the user should have in Ebbot

In your AD, the configuration of attributes can look something like this:

            <SubjectConfirmation Method="XXXX">
                <SubjectConfirmationData InResponseTo="XXXX" NotOnOrAfter="XXXX" Recipient=“”/>
        <Conditions NotBefore="XXXX" NotOnOrAfter="XXXX">
            <Attribute Name="Firstname">
            <Attribute Name="Lastname">
            <Attribute Name="Email">
            <Attribute Name="Roles">
        <AuthnStatement AuthnInstant="XXXXXX">

Please note that:

  • Skills are only relevant if they are included in your Ebbot setup

  • When setting the roles, make sure that there is only one role per person

To continue the configuration, you need a SP SAML entity descriptor metadata URL from Ebbot to insert in your AD.

You can set up yourself, a colleague or your Ebbot contact person as an Ebbot user in your AD to test if the configuration was successful.

Last updated