Description |
This article describes that the local Certificate is not selectable under SSL VPN settings, even though it is imported correctly |
Scope |
FortiGate v7.x.x+. |
Solution |
It is possible to run into a scenario where the Local Certificate is imported correctly, but it will not show up when trying to add it under SSL VPN Settings. This can happen especially if using custom PKI infrastructure (Active Directory, for example).
When creating a certificate in Active Directory using a Certificate Template, it is possible to choose whether it should be for 'Server Authentication' or 'Client Authentication'.
For the certificate to be selectable within the SSLVPN, or for the Admin GUI interface, it would need to be set to 'Server Authentication'. This is visible in the FortiGate by double-clicking the certificate, and scrolling down to 'Extensions'.
Below is an example of a correct certificate:
|
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.