description | topics | contentType | useCase | ||||
---|---|---|---|---|---|---|---|
A guide on installing the AD/LDAP Connector on different platforms. |
|
how-to |
|
This document covers how to install the AD/LDAP Connector on non-Microsoft Platforms.
::: warning Prior to installing the AD/LDAP Connector, please ensure that you have already installed Git, Node.js, and npm. :::
::: note For most platforms, you will need to run the required commands with root privileges. :::
-
-
Expand the package and install its dependencies:
mkdir /opt/auth0-adldap tar -xzf /tmp/adldap.tar.gz -C /opt/auth0-adldap --strip-components=1 cd /opt/auth0-adldap npm install
-
Start your server.
node server.js
When prompted for the ticket number, enter the full ticket URL from the Settings tab of the Setup AD/LDAP connector screen in the Auth0 Management Dashboard:
> Please enter the ticket number: https://YOUR_DOMAIN.auth0.com/some/other/stuff
-
You will be prompted to edit the
config.json
configuration file with your LDAP connection and authentication details:"LDAP_URL": "ldap://YOUR_LDAP_SERVER_FQDN", "LDAP_BASE": "dc=YOURDOMAIN,dc=com", "LDAP_BIND_USER":"YOUR_LDAP_USER", "LDAP_BIND_PASSWORD":"YOUR_LDAP_USER_PASSWORD" //cleartextpassword
::: note If you're using LDAP, refer to the Modifying the Connector Settings page. :::
-
Run
node server.js
once more to start the Connector. Note that theLDAP_BIND_PASSWORD
line inconfig.json
changes toLDAP_BIND_CREDENTIALS
at this point. -
Once the Connector is running, you will need to daemonize the Connector (if you don't already have a tool selected, you can consider upstart or systemd). For example, for using systemd with Ubuntu Xenial, the file
/lib/systemd/system/auth0-adldap.service
could contain the following:[Unit] Description=Auth0 AD LDAP Agent After=network.target [Service] Type=simple Restart=always User=ubuntu WorkingDirectory=/opt/auth0-adldap ExecStart=/usr/bin/node server.js
- Run
node admin/server.js
to access the admin UI -- the admin UI will be running and available onhttp://localhost:8357
.
::: note
If you get an Invalid Ticket
message when configuring the Connector for the first time, the most likely cause is a network issue (for example, you have the Connector running behind a proxy).
:::