Hi
I am currently developing our VPN solution that based only on certificate authentication (so no username, password or xauth). I succeeded in developing something for SSL-VPN which is running quiet fine but however... I have some difficulties with IPSec.
I nailed down my issue to a simple change in my configration. When I supply a configuration that explicitly mentions the certificate that is need like this:
<auth_data>
<mode>aggressive</mode>
<certificate>
<common_name>
<match_type><![CDATA[simple]]></match_type>
<pattern><![CDATA[My Name]]></pattern>
</common_name>
<issuer>
<match_type><![CDATA[simple]]></match_type>
<pattern><![CDATA[My CA]]></pattern>
</issuer>
</certificate>
</auth_data>
everything is working fine but as soon as I try it with a wildcard or regex like this:
<auth_data>
<mode>aggressive</mode>
<certificate>
<common_name>
<match_type><![CDATA[wildcard]]></match_type>
<pattern><![CDATA
</common_name>
<issuer>
<match_type><![CDATA[simple]]></match_type>
<pattern><![CDATA[My CA]]></pattern>
</issuer>
</certificate>
</auth_data> the connection is not working anylonger. However the Forticlient is showing the correct certificate in the certificate selection screen.
This issue only affects IPSec VPN. SSL-VPN works fine with the same certificate configuration. Any ideas what I might do wrong?
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.
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 |
---|---|
1688 | |
1087 | |
752 | |
446 | |
227 |
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.