3rd Party Authentication

3rd Party Authentication

Dengage supports third-party authentication mechanisms, including LDAP (Lightweight Directory Access Protocol).

This integration allows organizations to leverage their existing authentication infrastructure, ensuring a seamless and secure login experience for users. By using LDAP, Dengage can authenticate users against centralized directories, providing robust access control and simplifying user management. This feature enhances security, improves compliance, and streamlines the authentication process, making it easier to manage user identities and permissions within the platform.

This section provides an overview of the existing third-party authentication configurations.

3rd Party Authentication

3rd Party Authentication

To navigate this page to enable 3rd Party Integration, clicking this item will display the main page of this section as follows:

1.Overview:

This section provides an overview of the existing third-party authentication configurations.

Name: Displays the name of the authentication provider, identifying the service used for authentication.

Type: Specifies the type of authentication provider, such as LDAP.

📘

LDAP

Dengage currently only supports LDAP authentication.

Update Date: Indicates the date when the authentication configuration was last updated or modified.

2.Add:Users can add new third-party authentication configurations in this section.

  • Name: Users specify a name for the new authentication configuration, aiding in easy identification within the app.
  • Type: Users select the type of authentication provider they want to add from the available options.

How to Configure LDAP Parameters

Other Options for LDAP:

  • Domain: Users enter the domain associated with the authentication provider, ensuring correct routing of authentication requests.
  • Host name: Specifies the hostname or server address of the authentication provider's endpoint.
  • Port: Specifies the port number through which the app communicates with the authentication provider.
  • Username: Users provide their username or identifier for authenticating with the third-party service.
  • Password: Users enter their password associated with the provided username.
  • Use SSL (Checkbox): Users can choose to enable Secure Sockets Layer (SSL) encryption for secure communication with the authentication provider by checking this box.
  • Save: This option allows users to save the newly added authentication configuration. Once saved, the app will utilize the specified settings for third-party authentication, ensuring secure and seamless access to authorized users.
    • Related Articles

    • 3rd Party Integration

      This section provides a comprehensive guide to integrating Dengage with third-party platforms such as TikTok, Typeform, Shopify, Magento, WooCommerce, Salesforce, Mixpanel, WhatsApp, Microsoft Dynamics, and more. Each integration is explained in ...
    • Whatsapp Business API

      Dengage now supports direct integration with the WhatsApp Business API. Users can seamlessly set up and manage their WhatsApp messaging without relying on third-party providers. Once the integration is configured via Settings > Integrations > 3rd ...
    • Web Login

      This page allows you to restrict access to your web interface login. Logging in through the Web Interface is a crucial security matter. Anyone who gains access to your account can control various elements like your audience, segments, campaigns, etc. ...
    • Spam Checker

      This feature helps to improve the deliverability of email campaigns. Overview Email Spam Score feature uses the 3rd party tool named ‘Spam Assassin’. This tool is a simple tool that only receives email content and calculates the spam score of it. ...
    • MMS

      *Prerequisites: There should be 3rd party provider integration. The MMS Sending feature has been added to the existing SMS module, enabling customers to send Multimedia Messaging Service (MMS) content in addition to SMS. This enhancement offers ...