Skip to content

← All integrations

Firewall and VPN · Web server

Renews the frontend certificate on one FortiWeb policy or plain SNI domain.

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

What happens

  1. The appliance connects to Fortinet FortiWeb WAF through FortiWeb REST API on port 443.
  2. Select one server policy or plain SNI domain. The integration imports certificate and intermediates; the SNI group is copied so other policies and members retain their certificates.
  3. Only selected policy fields change. The binding is read back and the TLS leaf checked for up to 30 seconds; an unreachable listener gives configuration confirmation.

Technical details

Connection
The integration runs on the appliance, which connects over HTTPS to FortiWeb REST API, port 443. No service agent is installed.
Service ports
443
What you need
Create an administrator with read/write access to server policies and certificates. Set its trusted host to the address the jobs run from (the appliance or the server running the service agent). Enter that administrator's name and password here: FortiWeb has no separate API keys; REST uses administrator credentials.
Platform
FortiWeb 7.0, 7.2, 7.4, 7.6, 8.0
Actions
Discovery, Installation, Verification, Rollback
Integrations
fortiweb-api 1.0.0
Note
  • Restoration and rollback use previous_state and preserve later bindings. Native Let’s Encrypt selection is taken over only for the selected policy or copied SNI member; old objects remain. Multi-certificate and regex SNI targets are unsupported. There is no undeploy action. The certificate chain consists of the intermediate certificates that link the server certificate to a root certificate the browser trusts.

Certificate requirements

The integration accepts RSA 2048/3072/4096 and ECDSA P-256/P-384 as PEM with a matching unencrypted key. Vendor CSR choices are not universal import bounds.

Intermediates are ordered and placed in a new CA group; a self-signed root is omitted. Empty input replaces the previous intermediate group with an empty reference.

The certificate must suit frontend clients and names. Verification compares the served leaf; it does not promise a complete client test. General CN, KU/EKU, SAN-count and lifetime import bounds are not published in the listed sources.

Next steps