Overview
To enable communication between AD/LDAP and the Druva Cloud Platform, it is essential to establish a secured connection between your AD/LDAP and the Druva Cloud using the AD/LDAP Connector. To establish this connection, you must first download and install the AD/LDAP Connector on your system.
This article offers detailed steps for downloading and installing the AD/LDAP Connector on Windows and Linux operating systems.
π Note
Druva Cloud uses the AD/LDAP Connector only while authenticating and activating Druva administrators. The non-availability of AD/LDAP connectors does not impact the backup and restore activity.
Prerequisites
The following table lists the hardware and software prerequisites for installing an AD/LDAP Connector. The AD/LDAP Connector has minimal hardware/software requirements, making it compatible with almost any system.
Category | Minimum Requirements |
Hardware Prerequisites |
|
CPU | 1 GHz or faster |
RAM | 2 GB |
Disk Space | 16 GB π Note Ensure that the available disk space is at least twice the size of the installer file. |
Software Prerequisites |
|
Operating system | Windows
π Note For Windows Server 2012 users, the User Interface (UI) is supported for installation only. You can use Linux command-line instructions for activation. Linux
|
Download AD/LDAP Connector
To download the AD/LDAP Connector
From the Druva Cloud Platform console, go to the Druva Cloud Settings.
Click AD/LDAP Connectors > Add New Connector. The Add New Connector window appears.
βOn the Add New Connector page:
In the Select OS dropdown, select the Operating System (OS) and click Download. The AD Connector download starts on the same browser page.
You can download the AD Connector for the below-listed operating systems:For Windows: Windows - 64bit - msi
For Linux CentOS or REHL: Linux - all - rpm
For Linux Ubuntu: Linux - all - deb
Copy the default generated Registration Key. You will require the registration key to activate the connector after installation. You can also generate a new registration key by clicking on the Generate Key button.
β
βπ Note
One Registration Key can activate only one Connector. To activate another Connector, you must generate a new Registration Key.
ββ
Click Done. The AD/LDAP connector is now downloaded.
Install AD/LDAP Connector
On Windows
π Note
You must be a super user or an administrator to install the AD/LDAP Connector on your system.
To install the AD/LDAP Connector on Windows
Double-click the ADConnector agent installer. The installation wizard appears. Click Next.
Check the Cloud Services Customer Agreement and the privacy policy and select Next.
Specify the Installation location and select the appropriate checkboxes:
(Optional) Desktop Shortcut: You can create a desktop shortcut for the AD Connector installation wizard.
(Optional) Enable Signature Verification: Selecting this option ensures the integrity and authenticity of binaries. It also prevents the execution of any altered binaries, thereby safeguarding against malicious modifications or tampering with packages.
β
Click Install. The AD Connector is now successfully installed.
On Linux (CentOS, RHEL & Ubuntu)
π Note
You must be a super user or an administrator to install the AD/LDAP Connector on your system.
To install the AD/LDAP Connector on Linux
Navigate to the directory that contains the ADConnector agent installer.
Run the following command:
βFor CentOS & RHEL Linux
βrpm βivh <package name>
βExample:
βrpm βivh ADConnector-ADConnectorAgent-1.0.0-445290-x86_64.rpm
β
βFor Ubuntu
βdpkg -i <package_name>
βExample:
βdpkg -i ADConnector-ADConnectorAgent-1.0.0-445290-amd64.deb
β
where <package name> represents the file name (along with the extension) of the installer.Enter input as [yes/no] to enable signature verification.
β
βπ NotesBy default, the input option for enabling signature verification is [no].
The Enable Signature Verification option ensures the integrity and authenticity of binaries. It also prevents the execution of any altered binaries, thereby safeguarding against malicious modifications or tampering with the package.
β
(Optional) You can also verify the integrity and authenticity of the package See Package Signature Verification for more details.