Configure SSO in widget card

This guide explains how to configure SAML-based Single Sign-On (SSO) between Microsoft Azure Active Directory and the Ebbot widget.

Prerequisite – Get the Metadata File

Before starting the Azure configuration, you must generate the SAML metadata file in the widget.

  1. Go to Settings → Integrations → SSO in the widget.

  2. Click Save (this is required even if no changes are made).

  3. After saving, the metadata file will be available at one of the following URLs, depending on hosting:

    • EU OVH Hosting

      https://sp.saml.ebbot.eu/[botid]/metadata.xml
    • EU Google Hosting

      https://sp.saml.v2.ebbot.app/[botid]/metadata.xml
  4. Download and save the metadata file locally. You will need this file later when configuring SAML in Azure.

Create the Enterprise Application in Azure

  1. Go to Azure Portal and navigate to Enterprise Applications.

  2. Click New applicationCreate your own application.

  3. Enter a name for the application.

  4. Select Integrate any other application you don’t find in the gallery (Non-gallery).

  5. Click Create.

Configure Single Sign-On (SAML)

  1. Once the application is created, open it and click Set up single sign-on.

  2. Select SAML as the sign-on method.

  3. Click Upload metadata file.

  4. Upload the locally saved metadata file.

  5. Click Save.

Export and Configure the Certificate

  1. Download the Base64-encoded certificate from Azure.

  2. Go to settings --> integrations --> SSO in widget.

  3. Paste the certificate into the IDP Certificate field.

Encryption Options

  1. Choose one of the following options:

  • Upload the client certificate into Azure, or

  • Enable Allow Unencrypted Assertion

Testing and Attribute Mapping

  1. You can now start testing SSO directly inside the widget.

  2. The attributes under Attributes & Claims should be accessible using the {{ email }} attribute.

Final Step: Enable SSO in a Scenario

  1. Add the SAML SSO card to the scenario you want to authorize access through.

Last updated

Was this helpful?