Description |
This article describes how to use FortiAuthenticator as a CMPv2 server to rollout 3GPP certificates to FortiGates in SecGw for mobile network deployments. |
Scope |
FortiGate v6.2.x onwards, FortiAuthenticator v6.6.x onwards. |
Solution |
Find the steps below for setup :
On FortiAuthenticator :
Once enabled, select a server certificate and setup the default enrollment password:
Note: Can use HTTPS or HTTP - this example demonstrates TCP/80.
Note: Device vendor CA certificate would be the CA signing the FortiGate authentication certificate. In this example, 'Fortinet_Factory' certificate will be used on FortiGate, so the Fortinet CA certificate is selected.
The enrolment request can be customized as per requirement by setting appropriate renewal period and selecting required key usages. This will be seen in the 'Pending' status when created:
On FortiGate:
config certificate remote # edit G_REMOTE_Cert_1 (G_REMOTE_Cert_1) # get
execute vpn certificate local generate cmp <local name> <key size> <server-address:port> <path> <SrvCert> <AuthCert> <username> <password>
In this example:
execute vpn certificate local generate cmp SecGW-cert 2048 10.5.145.56:80 /app/cert/cmp2/ G_REMOTE_Cert_1 Fortinet_Factory Certificate CMP IR started, Please check it in a while
Successfully issued:
config certificate local edit SecGW-cert get name : SecGW-cert . .
Troubleshooting:
On FortiGate - the process can be tracked using CMP debugs below or by running sniffers to FortiAuthenticator IP:
diag debug reset diag debug app cmp 255 diag debug en
In captures on filtering CMP:
On FortiAuthenticator - debugs are available on Debug page -> Others -> SCEP/CMP. |
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.