How to Configure AD User login Authentication in Enforce for Data Loss Prevention 15.x and above
DLP 15.0 and Above
The process for setting up AD User Authentication in DLP changed in version 15.0. The configuration now takes place both in the UI and manual configuration of the springSecurityContext file.
In order to configure an LDAP AD Connection for Symantec DLP 15.0 and above, complete the following steps:
- Copy the springSecurityContext-KERBEROS.xml template from
- Paste the copied springSecurityContext-KERBEROS.xml file into the
- Rename the file to springSecurityContext.xml by removing the -KERBEROS from the file name, replacing the existing springSecurityContext.xml file.
- Since we are only configuring an Active Directory connection, we do not need to edit the contents of this file.
- Change to the
SymantecDLPProtectconfigon Windows or
- Edit the krb5.ini file (krb5.conf on Linux), adding information about the Active Directory domain structure and server location(s). More than one location can be defined if needed, as seen in screen shot below. The
[libdefaults]section identifies the default domain. (Kerberos realms correspond to Active Directory domains.) The
[realms]section defines an Active Directory server for each domain. In the example below, the Active Directory server for ENG.COMPANY.COM is acmeADserver.company.com. More than one server can be added, as needed.
- Restart the DLP Services,
- Log in to DLP Dashboard in the browser
- Add an Active Directory Connection in the Symantec DLP dashboard under System > Settings > Directory Connections.
- Add User Roles (as needed) under System > Login Management > Roles
- Add a user inside the DLP Dashboard under System > Login Management > DLP Users (You must still define users in the Enforce Administration Dashboard, before an AD user can successfully login. The user names entered in the DLP Dashboard will be cross-checked with Active Directory usernames / passwords. You can switch to Active Directory authentication after you have already created user accounts in the system. Only those existing user names that match Active Directory user names remain valid after the switch.)
If you are running Symantec Data Loss Prevention on Linux, verify the Active Directory connection using the kinit utility. You must rename the krb5.ini file as krb5.conf. The kinit utility requires the file to be named krb5.conf on Linux. Symantec DLP assumes that you use kinit to verify the Active Directory connection, and directs you to rename the file as krb5.conf.