Skip to content

← All integrations

Firewall and VPN

Imports the certificate and swaps the admin, SSL-VPN and IPsec certificate references.

The appliance runs the integration and connects to Fortinet FortiGate through FortiOS REST API over HTTPS on port 443. No service agent is installed on Fortinet FortiGate.

What happens

  1. The appliance connects to Fortinet FortiGate through FortiOS REST API on port 443.
  2. The integration imports a new local certificate with key and adds missing intermediates to the CA store. Selected admin HTTPS, SSL VPN and existing IPsec bindings are updated.
  3. Bindings are read back. Admin HTTPS and SSL VPN with a specified port are checked over TLS; an unreachable listener gives configuration confirmation with a warning.

Technical details

Connection
The integration runs on the appliance, which connects over HTTPS to FortiOS REST API, port 443. No service agent is installed.
Service ports
443
What you need
System > Admin Profiles > Create New: set System and VPN to Read/Write. System > Administrators > Create New > REST API Admin: choose that profile and add this appliance's address under Trusted Hosts. Click OK and copy the token now; it is shown only once. Paste it here as the REST API token.
Platform
FortiOS 7.2.0+
Actions
Discovery, Installation, Verification, Rollback, Removal
Integrations
fortigate-api 2.0.0
Note
  • Restoration and rollback use previous_state and previous certificates. Later bindings are preserved; an unused import can be removed while CA entries remain. Selecting a native ACME binding moves the binding; FortiGate’s original certificate and renewal are retained. The certificate chain consists of the intermediate certificates that link the server certificate to a root certificate the browser trusts. ACME is the protocol a CA uses to issue certificates automatically.

Next steps