Technical Tip: TACACS+ and LDAP-proxy authentication stopped working after upgrading to FortiOS v7.4.4
| Description | This article describes a recent change made in FortiOS v7.4.4 that affects TACACS+ and LDAP-proxy authentication. More specifically, authentication may begin failing due to a connection timeout, even when it worked before upgrading the firmware. |
| Scope | FortiGate v7.4.4. |
| Solution | Starting FortiOS v7.4.4, a few changes were made in the fnbamd process that handles the authentication on the FortiGate against a remote server. One of the changes resulted in enforced certificate validation for LDAPS connections, requiring admins to upload the LDAPS server’s CA certificate to the FortiGate.
See the following KB article for more information: Technical Tip: LDAPS connections no longer work after update to v7.4.4
2024-06-03 08:11:44 [505] __tac_plus_conn_timeout-Connction withTACACS_SERVER:1.2.3.4 timed out. --> The packet capture indicates that the TACACS+ reply was reached after the FIN packet was sent from FortiGate.
To work around this issue, for LDAPS or TACACS+, change the ldapconntimeout to 2000ms or greater. If LDAP-proxy on the FortiGate is configured, then change ldapconntimeout to a similar value as remoteauthtimeout using the below commands:
config sys global set ldapconntimeout <time-in-milliseconds> end
This new ldapconntimeout value will help to account for any delays with LDAPS or TACACS+ packets, and it will also provide users with enough time to respond to multi-factor push notifications when using LDAP-proxy with MFA.
This issue has been resolved in FortiOS versions 7.4.5 and 7.6.1. |

