We are encountering an issue with users connecting to our VPN web portal via Fortinet using their Active Directory (AD) credentials. Specifically, when a user's password has expired and Fortinet prompts them to create a new one, the portal fails to validate whether the new password complies with AD's complexity requirements.
As a result, Fortinet provides a confirmation that the password has been successfully changed, despite the update not being propagated to the AD. This discrepancy causes users to believe their password has been updated, when in reality, the original password remains active. Consequently, users frequently contact support after being unable to authenticate using their "new" password.
Is there a way to enforce AD password policy compliance directly within Fortinet or otherwise mitigate this issue to reduce user confusion and support overhead?
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
The FortiGate has no knowlege of password complexity on the remote LDAP server, but if the change fails, it should be propagated as an error response to the password change attempt in the LDAP protocol. It's not expected to fail silently.
Check if the permissions are correct, and maybe do a test with an expired account via CLI.
Relevant doc: https://community.fortinet.com/t5/FortiGate/Technical-Tip-Enable-expired-password-LDAP-renewal-with-...
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1665 | |
1077 | |
752 | |
446 | |
220 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.