Help

Integration

Active Directory Password Filter

Updated 21 Nov 2026 10 min read

This page describes the Monosign AD Password Filter for Monosign v2026.11 and later: what it does, what it needs, how to install, configure and operate it. Problems, logs and fixes: Active Directory Password Filter Troubleshooting.

What it does

The filter runs on your domain controllers and connects every Active Directory password change to Monosign:

  • Password check: when a password is set in Active Directory (Ctrl+Alt+Del, Active Directory Users and Computers, PowerShell, any tool), the domain controller asks Monosign whether it meets the Monosign password policy before Active Directory accepts it.

  • Monitor or block: in Monitor mode every password is accepted and the ones that break the policy are listed. When you turn on blocking, such a password is refused and the user chooses another one.

  • Password sync: after Active Directory accepts a password, Monosign records it: an audit entry, the user's expired or must-change state cleared and, when the source keeps passwords, a stored copy.

  • Activity and health of every domain controller on the source's Password Filter tab in Management.

It never blocks a password because of a problem on the Monosign side (fail-open): no answer in time, Monosign down, or a user Monosign does not know all let the password through.

How it works

  1. A small password filter DLL (MonosignADPF.dll) is registered in the domain controller's LSA. Windows calls it for every password change on that domain controller.

  2. The DLL hands the password to the local Monosign AD Password Filter service over a local pipe. Both sides check each other: the DLL hands a password only to the installed service, and only lsass may talk to the service.

  3. The service asks Monosign (HTTPS) for the policy check and waits at most the answer wait (3 seconds by default).

  4. After Active Directory accepts the password, the service sends it to Monosign. If Monosign cannot be reached, it waits encrypted on the domain controller and is sent later. A password waits 24 hours at most, and a domain controller keeps at most 100,000 waiting changes (200 MB). Beyond these limits Monosign only records that the password changed (Sync missed).

  5. Every 30 seconds the service reports its health to Monosign; it reads the settings of the Password Filter tab every minute.

Only the domain controller where a password changes calls the filter, so every writable domain controller needs it. The tab lists the writable domain controllers that do not have it yet.

Requirements

Area

Requirement

Domain controllers

Every writable domain controller of the domain (read-only domain controllers never call password filters). Windows Server 2016 or later, x64.

Rights

A Domain Admin (or local administrator on the domain controller) to run the installer in PowerShell as administrator.

Restart

One restart of each domain controller after the first install: Windows loads password filters at startup. Upgrades usually need none.

Network

HTTPS (443) from each domain controller to the Monosign API URL. The address must start with https://; the installer refuses any other. Nothing is needed from Monosign to the domain controller.

Install on every domain controller

Only for More options > Install on every domain controller and Upgrade every domain controller: PowerShell remoting (WinRM) from the domain controller where you run the command to the other domain controllers.

Disk

At least 1 GB free on the system drive of each domain controller.

LSA protection

Not supported yet. On a domain controller with LSA protection (RunAsPPL) turned on, Windows does not load the filter DLL. The filter installs but stays inactive there: password changes work as usual, but they are neither checked nor synced. The installer tells you when LSA protection is on, and the domain controller's status names it. See Active Directory Password Filter Troubleshooting.

Monosign

v2026.11 or later, after the database upgrade (it creates the AD Password Filter application).

User source

An Active Directory user source whose users are synced to Monosign. Users are matched by their Active Directory account (objectSid).

Runtime

Nothing to install: the service is self-contained and the DLL has no dependencies.

Download

The install command on the Password Filter tab downloads everything itself. For a domain controller without internet access, download the files here.

File

Use

SHA-256

Install-MonosignADPF.ps1 (opens in a new tab)

Installer, upgrade and removal script for the latest release.

Signed PowerShell script

monosign-ad-password-filter-win-x64.zip (opens in a new tab)

Package of the latest release (the script installs it).

monosign-ad-password-filter-win-x64.zip.sha256 (opens in a new tab)

The installer checks the package's SHA-256 and installs only files that carry Monofor's signature. A file signed by anyone else stops the installation before anything is changed.

Components

Component

Where

Role

Password filter DLL

C:\Windows\System32\MonosignADPF.dll, entry MonosignADPF in HKLM\SYSTEM\CurrentControlSet\Control\Lsa\Notification Packages

Called by Windows for every password change. Holds no settings and never calls the network.

Monosign AD Password Filter service

Service MonosignADPF, C:\Program Files\Monofor\Monosign AD Password Filter\monosign-adpf.exe, automatic

Policy check, password sync, health reports. Runs as Network Service with its own service SID.

Command line

monosign-adpf.exe status, pause, resume, mode, sync, timeout

Health and per-domain-controller overrides (see Settings).

Data folder

C:\ProgramData\Monofor\Monosign AD Password Filter

config.json, the connection key (secret.bin, DPAPI-protected), waiting passwords (queue, encrypted), undelivered records (outbox, at most 100,000; they never contain a password), records Monosign refused (outbox\bad), health.json, logs. Readable only by SYSTEM, Administrators and the service.

Event log

Windows Application log, source Monosign AD Password Filter

Start, stop and problems of the DLL and the service.

Backups: a backup of a domain controller includes the data folder, with the connection key and any waiting passwords. Both are encrypted for that domain controller. Protect these backups as you protect every domain controller backup.

Prepare Monosign

  1. Run the database upgrade of v2026.11 (seed). It creates the AD Password Filter application with only the permissions the filter needs. Do not change its permissions.

  2. Open Management > Directory > Sources > (your Active Directory source) > Settings > Password > Password Filter. The tab shows the next step at the top.

  3. Choose the password policy: the filter checks against the source's own policy when Override Policy is on in the Password tab (and Allow Password Change is on for the source), otherwise against the global password policy.

  4. For a stored copy of synced passwords, the source needs Password Management set to By Provider and Keep Password Changes on.

Installation

  1. On the Password Filter tab, press Get install command. The command is valid for 24 hours and connects this source: keep it private.

  2. On a writable domain controller, open PowerShell as administrator, paste the command and press Enter. The installer downloads and checks the package, installs the service, checks that it keeps running for 30 seconds and only then registers the DLL.

  3. Restart the domain controller when it suits you. Until the restart the filter is installed but not active; the tab says so.

  4. After the restart the domain controller shows Healthy on the tab and follows the tab's settings. A new source starts in Monitor mode: nothing is blocked.

  5. Repeat on every writable domain controller, or use More options > Install on every domain controller, which installs on all of them and restarts them one at a time.

The command has this shape:

iwr https://download.monofor.com/monosign/agents/Install-MonosignADPF.ps1 -OutFile $env:TEMP\Install-MonosignADPF.ps1 -UseBasicParsing; & $env:TEMP\Install-MonosignADPF.ps1 -Url <Monosign API URL> -SetupKey <setup key>

Without internet on the domain controller

Download both files from More options > No internet on the domain controller (or from Download above), copy them to the domain controller and add -PackagePath <path of the zip> to the install command.

Upgrade

Copy Upgrade from Commands for a domain controller and run it on the domain controller (or More options > Upgrade every domain controller). It keeps the domain controller's settings and key and needs no setup key. A restart is needed only when the DLL itself changed; the upgrade says so. If the new version does not keep running, the previous one is restored automatically.

Settings

Set on the Password Filter tab under Settings; every domain controller of the source applies them within a minute.

Setting

Default

Meaning

Check passwords

Yes

New passwords must meet the password policy. Off: only Active Directory's own rules apply.

Block weak passwords

No

Yes: a password that breaks the policy is refused and the user chooses another one. No (Monitor): it is accepted and listed in Activity as Would reject (Monitor).

Sync passwords to Monosign

Yes

Password changes made in Active Directory are recorded in Monosign.

Let administrators see synced passwords

No

Shown only when a copy is kept. Yes: the stored password can be shown in Password Keep.

Advanced > Answer wait

3 seconds

How long a domain controller waits for Monosign (0.5–10 seconds). With no answer in time the password is accepted and Activity shows Check skipped.

Advanced > Exclusions

none

Accounts that are never checked or synced, such as service accounts. One pre-Windows 2000 account name per line; end a name with * to match every name that starts with it.

Start with blocking off. When the Activity tab shows only expected Would reject (Monitor) lines, turn on Block weak passwords (the next-step card offers Turn on Enforce).

A domain controller can override any of these for itself in its config.json, or with monosign-adpf.exe mode <Off|Monitor|Enforce|default>, sync <On|Off|default> and timeout <milliseconds|default>. Its row on the tab then says set on this DC; default hands the value back to the tab.

Built in and the same everywhere:

  • Computer accounts (names ending in $), krbtgt and Exchange health mailboxes (HealthMailbox followed by 7 hex characters, whose passwords Exchange sets itself) are never checked or synced.

  • After 3 checks in a row get no answer, checks are skipped for 30 seconds.

  • A domain controller checks up to 64 password changes at the same moment. In a larger burst (a bulk reset, for example) the extra changes are accepted without the check and shown as Check skipped.

Operate

Domain controllers on the tab: one row per domain controller with its status, mode and last report.

Status

Meaning

Healthy

Running and reporting.

Paused

Paused on purpose: passwords are neither checked nor synced.

Needs attention

Running with a problem; the reason is shown under the status.

Not reporting

No report for 2 minutes: the service is stopped or the domain controller is down. Password changes there are not affected.

Not installed

A writable domain controller of the domain without the filter: a password changed there is neither checked nor synced.

Removed

The filter was removed from this domain controller.

Commands for a domain controller (copy and run in PowerShell as administrator on that domain controller):

Command

Use

Check health

Healthy, or what is wrong.

Pause now

The filter does nothing from this moment. No restart. Works even when the service cannot run.

Resume

Back to normal. No restart.

Upgrade

Newest version, see Upgrade above.

Remove

Pauses first and removes everything; restart the domain controller when it suits you.

Check removal (after the restart)

Every line must say OK.

Activity lists the last 30 days, newest first; search a user name to see that user's password audits, or turn on Problems only.

Result

Meaning

Synced

Monosign received the new password.

Already current

Monosign already had this password (for example it was set through Monosign).

Not a Monosign user

The account is not in Monosign: accepted and not synced.

Several users

Several Monosign users match the account: nothing was synced.

Would reject (Monitor)

The password breaks the policy; Monitor accepted it.

Rejected by policy

Blocked: the user had to choose another password.

Check skipped

Monosign did not answer in time, or the domain controller was handling more password changes than it can check at once; the password was accepted without a check.

Sync missed

The password could not be handed over; Monosign only knows that it changed.

Audit

Audit

When

Password changed in the directory / Password reset in the directory (USER_PASSWORD_CHANGED_PROVIDER), origin AD Password Filter (<domain controller>)

A synced password was recorded.

Password Sync Missed (USER_PASSWORD_SYNC_MISSED)

Active Directory accepted a password that Monosign never received.

Password Policy Check Skipped (USER_PASSWORD_POLICY_SKIPPED)

Active Directory accepted a password without the policy check.

ACCESS_RESTRICTION

A password failed the policy check.

No audit and no activity line ever contains a password.

Uninstall and recovery

Copy Remove from the tab and run it on the domain controller. It pauses the filter at once, removes its LSA entry, the service and the files, and keeps the filter paused until the restart. Restart the domain controller, then run Check removal (after the restart): every line must say OK.

To stop the filter immediately without removing it, use Pause now: no restart, and it works even when the service cannot start.

If a domain controller cannot start normally because of the filter, remove MonosignADPF from HKLM\SYSTEM\CurrentControlSet\Control\Lsa\Notification Packages and restart, or, in Directory Services Restore Mode, delete C:\Windows\System32\MonosignADPF.dll.

Related pages

Permanent link