What the Active Directory integration does
Each client's users, licenses and managed devices sit next to the rest of their documentation, refreshed automatically.
Setting it up
When DokLocker runs on your own network, people can sign in with their Windows password, checked by your domain controllers.
- Create a read-only service account in Active Directory (a normal domain user is enough).
- Choose Active Directory (LDAP) and enter a domain controller (
ldaps://dc01.yourcompany.local), the search base (DC=yourcompany,DC=local), the service account and its password, and the email domains that sign in this way. - To limit who can sign in, enter a group's distinguished name. Members of groups inside that group count too.
- Click Test.
For those email domains, the domain controller is the only judge: the DokLocker password no longer works for them, and a disabled or locked Active Directory account can't sign in. Wrong passwords still count towards DokLocker's own lockout. Use ldaps:// so passwords are encrypted on the network; if your domain controllers use a certificate from your own certificate authority and DokLocker doesn't trust it, choose Allow a self-signed certificate.
Included in every plan
Every integration is included at no extra cost, on the hosted service and self-hosted. Connect it under Admin › Integrations, click Test, and the first sync starts straight away.