Cisco Secure Firewall (FDM)
Copy link to the page “Cisco Secure Firewall (FDM)”Uploads or renews certificate objects and binds them to the Web UI, RA VPN and the other targets discovery found.
What happens
- The appliance connects to Cisco Secure Firewall (FDM) through FDM API on port 443.
- Select WebUI, RA VPN, a known-key SSL policy or site-to-site VPN. The integration uploads a new internal certificate and retains the previous one; WebUI also receives its CA chain.
- The target reference changes and is deployed. WebUI and RA VPN are checked over TLS where reachable; SSL policy and site-to-site VPN are confirmed through configuration.
Technical details
- Connection
- The integration runs on the appliance, which connects over HTTPS to FDM API, port 443. No service agent is installed.
- Service ports
- 443
- What you need
- Use the admin account, or Objects > Users > + : a local user with Service Types MGMT and User Role Administrator, then deploy. Enter that user name and password here. The appliance must reach the FDM's management address on HTTPS; with an HA pair, add the active unit.
- Platform
- FTD/FDM 6.4+, WebUI CA chain 6.6+
- Actions
- Discovery, Installation, Verification, Rollback
- Integrations
-
cisco-fdm-api2.0.0 - Note
-
- Pending changes stop the run by default; force_deploy_all includes them. Automatic restoration and rollback use previous_state and preserve later bindings. There is no undeploy action, and running deployment is not raced by restoration. The certificate chain consists of the intermediate certificates that link the server certificate to a root certificate the browser trusts.