Description |
This article describes the case when the CN of the peer's certificate is similar or shares a common value, then FortiGate might match the SSL VPN user with the first peer config that has a slimmer CN. As a result, SSL VPN may hit the wrong user group and traffic might hit the wrong firewall policy.
config user peer
Each peer has been enabled in a different group (and has been enabled on a different firewall policy as well):
When both SSL VPN users are connecting with two different certificates (which have different CN), on FortiGate both users matched the first peer 'pki01' since both peers have 'testpki' in common in CN:
FGT # get vpn ssl monitor SSL VPN sessions: Index User Group Source IP Duration I/O Bytes Tunnel/Dest IP |
Scope | FortiGate. |
Solution |
The subject-match must be changed from 'substring' to 'value', 'substring' is the default setting.
config vpn certificate setting
Note: If VDOM is enabled, the changes should be done per VDOM:
config vdom
FGT # get vpn ssl monitor SSL-VPN sessions: |
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 2025 Fortinet, Inc. All Rights Reserved.