From 5036d6da5368d16ba12270b3d1746432c3dd5f4c Mon Sep 17 00:00:00 2001 From: Bryan Nelson Date: Mon, 10 Aug 2026 10:58:03 -0400 Subject: [PATCH 1/2] Add KB article on Fortinet Authenticator credential provider allowlist Documents adding the Password Policy Enforcer Client GUID to Fortinet's CredentialProvidersWhiteList registry value so password policies display correctly when both products are installed. Co-Authored-By: Claude Sonnet 5 --- ...forcer-client-in-fortinet-authenticator.md | 52 +++++++++++++++++++ 1 file changed, 52 insertions(+) create mode 100644 docs/kb/passwordpolicyenforcer/authentication-and-integration/allow-netwrix-password-policy-enforcer-client-in-fortinet-authenticator.md diff --git a/docs/kb/passwordpolicyenforcer/authentication-and-integration/allow-netwrix-password-policy-enforcer-client-in-fortinet-authenticator.md b/docs/kb/passwordpolicyenforcer/authentication-and-integration/allow-netwrix-password-policy-enforcer-client-in-fortinet-authenticator.md new file mode 100644 index 0000000000..8f8817f2b2 --- /dev/null +++ b/docs/kb/passwordpolicyenforcer/authentication-and-integration/allow-netwrix-password-policy-enforcer-client-in-fortinet-authenticator.md @@ -0,0 +1,52 @@ +--- +description: >- + Steps to configure Fortinet Authenticator to work with Netwrix Password Policy Enforcer Client by adding the Password Policy Enforcer Client GUID to the Fortinet CredentialProvidersWhiteList + registry value. +keywords: + - Netwrix Password Policy Enforcer + - Fortinet Authenticator + - CredentialProvidersWhiteList + - registry + - GUID + - Windows Logon + - credential provider + - Password Policy Enforcer Client + - CTRL+ALT+DEL + - filter acceptance list +products: + - passwordpolicyenforcer +sidebar_label: Password Policies Not Displaying When Fortinet Authenticator Is Installed +tags: + - kb +title: "Password Policies Not Displaying When Fortinet Authenticator Is Installed" +knowledge_article_id: +--- + +# Password Policies Not Displaying When Fortinet Authenticator Is Installed + +## Symptom + +Netwrix Password Policy Enforcer Client does not show password policies for users on machines running Fortinet Authenticator. + +## Cause + +Fortinet Authenticator filters out all other credential providers unless the filter acceptance list for Fortinet includes them. + +## Resolution + +1. Uninstall Password Policy Enforcer Client and Fortinet Authenticator, then reboot the machine. + +2. Install Fortinet Authenticator peforming a reboot and making sure Fortinet is working as expected. + +3. Apply the CredentialProvidersWhiteList to Fortinet location using the Password Policy Enforcer Client GUID: `{F347212E-AF6B-4726-92B3-E4DF3388D58C}` +> **NOTE:** More information on the Fortinet Registry is available in Fortinet documentation here: https://docs.fortinet.com/document/fortiauthenticator/6.6.0/fortiauthenticator-agent-for-microsoft-windows-5-1-install-guide/395640/appendix-d-fortiauthenticator-agent-for-microsoft-windows-registry-files + +4. Install Password Policy Enforcer Client, reboot, and make sure Fortinet Authenticator is still working as expected. + +5. After logging in, press CTRL+ALT+DEL and check whether password policies appear. An administrator must assign a password policy to the user for this to work. +> **NOTE:** If password policies still don't appear, wait on the CTRL+ALT+DEL > Change Password screen to see whether Password Policy Enforcer Client returns a communication error or the screen times out back to the CTRL+ALT+DEL screen. If it times out back to the CTRL+ALT+DEL screen, repeat the steps and verify that the GUID in the CredentialProvidersWhiteList registry value is correct and doesn't have missing or extra characters. + + +## Related articles + +- Appendix D - FortiAuthenticator Agent for Microsoft Windows registry files ⸱ FortiAuthenticator Agent for Microsoft Windows 5.1 Install Guide: https://docs.fortinet.com/document/fortiauthenticator/6.6.0/fortiauthenticator-agent-for-microsoft-windows-5-1-install-guide/395640/appendix-d-fortiauthenticator-agent-for-microsoft-windows-registry-files \ No newline at end of file From b727e3762ece124410161827905b407cfb4920bc Mon Sep 17 00:00:00 2001 From: hilram7 <212961752+hilram7@users.noreply.github.com> Date: Thu, 20 Aug 2026 22:46:06 -0700 Subject: [PATCH 2/2] Fix Vale/Dale/Derek findings in Fortinet Authenticator KB article - Vale: spell out contractions, fix heading case on "Related Articles" - Dale: fix dangling modifier and wordy phrasing in Steps 2-3, fix "peforming" typo - Derek: backtick the CredentialProvidersWhiteList registry value name, normalize Ctrl+Alt+Delete capitalization, convert bare URL to a markdown link, fix NOTE blockquote indentation under numbered steps, remove redundant Related Articles section (duplicated the sole in-body link, below the 3-link threshold) --- ...y-enforcer-client-in-fortinet-authenticator.md | 15 ++++++--------- 1 file changed, 6 insertions(+), 9 deletions(-) diff --git a/docs/kb/passwordpolicyenforcer/authentication-and-integration/allow-netwrix-password-policy-enforcer-client-in-fortinet-authenticator.md b/docs/kb/passwordpolicyenforcer/authentication-and-integration/allow-netwrix-password-policy-enforcer-client-in-fortinet-authenticator.md index 8f8817f2b2..8660800960 100644 --- a/docs/kb/passwordpolicyenforcer/authentication-and-integration/allow-netwrix-password-policy-enforcer-client-in-fortinet-authenticator.md +++ b/docs/kb/passwordpolicyenforcer/authentication-and-integration/allow-netwrix-password-policy-enforcer-client-in-fortinet-authenticator.md @@ -36,17 +36,14 @@ Fortinet Authenticator filters out all other credential providers unless the fil 1. Uninstall Password Policy Enforcer Client and Fortinet Authenticator, then reboot the machine. -2. Install Fortinet Authenticator peforming a reboot and making sure Fortinet is working as expected. +2. Install Fortinet Authenticator, reboot the machine, and confirm Fortinet Authenticator works as expected. -3. Apply the CredentialProvidersWhiteList to Fortinet location using the Password Policy Enforcer Client GUID: `{F347212E-AF6B-4726-92B3-E4DF3388D58C}` -> **NOTE:** More information on the Fortinet Registry is available in Fortinet documentation here: https://docs.fortinet.com/document/fortiauthenticator/6.6.0/fortiauthenticator-agent-for-microsoft-windows-5-1-install-guide/395640/appendix-d-fortiauthenticator-agent-for-microsoft-windows-registry-files +3. Add the Password Policy Enforcer Client GUID (`{F347212E-AF6B-4726-92B3-E4DF3388D58C}`) to the `CredentialProvidersWhiteList` registry value on the Fortinet machine. -4. Install Password Policy Enforcer Client, reboot, and make sure Fortinet Authenticator is still working as expected. - -5. After logging in, press CTRL+ALT+DEL and check whether password policies appear. An administrator must assign a password policy to the user for this to work. -> **NOTE:** If password policies still don't appear, wait on the CTRL+ALT+DEL > Change Password screen to see whether Password Policy Enforcer Client returns a communication error or the screen times out back to the CTRL+ALT+DEL screen. If it times out back to the CTRL+ALT+DEL screen, repeat the steps and verify that the GUID in the CredentialProvidersWhiteList registry value is correct and doesn't have missing or extra characters. + > **NOTE:** More information on the Fortinet Registry is available in [FortiAuthenticator Agent for Microsoft Windows Registry Files](https://docs.fortinet.com/document/fortiauthenticator/6.6.0/fortiauthenticator-agent-for-microsoft-windows-5-1-install-guide/395640/appendix-d-fortiauthenticator-agent-for-microsoft-windows-registry-files). +4. Install Password Policy Enforcer Client, reboot, and make sure Fortinet Authenticator is still working as expected. -## Related articles +5. After logging in, press Ctrl+Alt+Delete and check whether password policies appear. An administrator must assign a password policy to the user for this to work. -- Appendix D - FortiAuthenticator Agent for Microsoft Windows registry files ⸱ FortiAuthenticator Agent for Microsoft Windows 5.1 Install Guide: https://docs.fortinet.com/document/fortiauthenticator/6.6.0/fortiauthenticator-agent-for-microsoft-windows-5-1-install-guide/395640/appendix-d-fortiauthenticator-agent-for-microsoft-windows-registry-files \ No newline at end of file + > **NOTE:** If password policies still do not appear, wait on the Ctrl+Alt+Delete > Change Password screen to see whether Password Policy Enforcer Client returns a communication error or the screen times out back to the Ctrl+Alt+Delete screen. If it times out back to the Ctrl+Alt+Delete screen, repeat the steps and verify that the GUID in the `CredentialProvidersWhiteList` registry value is correct and does not have missing or extra characters. \ No newline at end of file