FortiGate
FortiGate Next Generation Firewall utilizes purpose-built security processors and threat intelligence security services from FortiGuard labs to deliver top-rated protection and high performance, including encrypted traffic.
Talank
Staff
Staff
Article Id 422658
Description

This article describes how to troubleshoot FortiGate SSL VPN failures where the FortiClient displays the error:


Credential or SSLVPN configuration is wrong (-7200)

 

This applies to SSL VPN Tunnel Mode and is valid regardless of the authentication type (Local, LDAP, RADIUS, MFA, etc.).

Scope FortiGate.
Solution

Symptoms:

 

Screenshot 2025-12-11 161441.png

 

Additionally, the firewall debug logs show a successful TLS handshake, but authentication ultimately fails with an unknown reason.


Observed Logs:

Below is a snippet showing a successful TLS handshake negotiation followed by a login failure:

 

SSL established: TLSv1.3 TLS_AES_128_GCM_SHA256  <--
user 'testTAC' has a matched local entry.
two factor check for testTAC: off
authenticate user: [testTAC]
[fam_auth_send_req] Groups sent to FNBAM:
... (multiple groups)
login_failed:497 user[testTAC],auth_type=1 failed [sslvpn_login_unknown_reason]  <--

 

FortiGate requires the SSL cipher strength in vpn ssl settings to be equal to or stronger than the cipher strength in the authentication-rule.

 

If the SSL settings define a weaker cipher, FortiGate completes the TLS handshake but fails at user authentication, resulting in the (-7200) error.

Incorrect configuration:

 

config vpn ssl settings
    set ssl-min-proto-ver tls1-3
    set banned-cipher SHA256
    set ciphersuite TLS-AES-128-GCM-SHA256 --> Lower strength 128 bits.
    set servercert "Fortinet_Factory"
    set idle-timeout 1800
    set tunnel-ip-pools "SSLVPN-TUNNEL"
    set dns-server1 10.3.1.8
    set dns-server2 10.1.2.100
    set port 49153
    set source-interface "port30"
    set source-address "all"
    set default-portal "No-Access"

        config authentication-rule --> Default is 168-bit cipher strength.
            edit 1
                set groups "Test-Group"
                set portal "SSLVPN_CORONA"
            next
end

 

In this case, the solution is to increase the strength of the ciphersuite to a higher value (>= 168 bits), or unset the ciphersuite to the default value.