Skip to main content

Configuring LDAP authentication

You can use fixed enrollment accounts or an LDAP directory, such as Active Directory, eDirectory, or Open Directory, for MDM enrollment authentication. This setup edits /usr/local/filewave/apache/conf/mdm_auth.conf on the FileWave Server, so self-managed customers need server shell access. Hosted FileWave customers should work with FileWave Technical Support because they do not have direct server file access. Complete this before enrolling MDM clients.
The process has three parts:

    1. Back up the current config file;
    2. Edit a new config file so it can read the LDAP structure; and
    3. Restart the Apache process so it reads the new config file.

Getting the files ready

  • Open a Terminal window or use SSH to access the computer running FileWave Server
  • Gain root credentials
sudo -s
  • Enter your login password
  • Navigate to the FileWave Apache configurations folder:
cd /usr/local/filewave/apache/conf/
  • Back up your current mdm_auth.conf by making a copy
cp mdm_auth.conf mdm_auth.conf.bac
  • Make a copy of the LDAP example and rename it
cp mdm_auth.conf.example_ldap_auth mdm_auth.conf
  • Make the changes
  • Open mdm_auth.conf in your preferred text editor, such as nano mdm_auth.conf or vi mdm_auth.conf. The sample file is commented; update it for your LDAP structure, then save the .conf file.

If you edit the file outside the server shell, copy it back to /usr/local/filewave/apache/conf/mdm_auth.conf with the correct filename before restarting Apache.

Note: Active Directory (AD) normally requires a bind account before FileWave can read the directory. Many organizations create a read-only directory account for this purpose.

  • Once saved, restart the FileWave Apache process/service:
/usr/local/filewave/apache/bin/apachectl graceful

Now, when a user attempts to enroll a device in your MDM server, they can use their LDAP credentials to authenticate.

Related Content

No comments to display

Back to top