Fortinet Triggers
This section details how to configure the Triggers that will be used by Profiles to push or delete certificates to/from Fortinet appliances.
FortiGate Trigger
How to configure FortiGate Trigger
1. Log in to Horizon Administration Interface.
2. Access FortiGate Triggers from the drawer or card: .
3. Click on 
.
4. Fill the mandatory fields.
-
Name* (string input):
Enter a meaningful trigger name. It must be unique for each trigger. Horizon uses the name to identify the trigger. -
FortiGate Connector* (select):
Select a FortiGate connector previously created. -
Retries in case of error (int):
Number of times to retry to push the change on the FortiGate in case of error. Must be an integer between 1 and 15.
5. Click on the save button.
You can update 
or delete 
the FortiGate Trigger.
FortiManager Trigger
How to configure FortiManager Trigger
1. Log in to Horizon Administration Interface.
2. Access FortiManager Triggers from the drawer or card: .
3. Click on .
4. Fill the mandatory fields.
-
Name* (string input):
Enter a meaningful trigger name. It must be unique for each trigger. Horizon uses the name to identify the trigger. -
FortiManager Connector* (select):
Select a FortiManager connector previously created. -
Retries in case of error (int):
Number of times to retry to push the change on the FortiManager in case of error. Must be an integer between 1 and 15.
5. Click on the save button.
You can update or delete the FortiManager Trigger.
Synchronization using triggers
Triggers are a functionality of WebRA, EST, Intune PKCS, WCCE and CRMP profiles that allows to push lifecycle events into a third party whenever they occur on a profile.
1. Refer to the trigger documentation to create a trigger.
2. Create or modify the profile you wish to use the triggers on.
3. Go to the Triggers tab, then on Certificate lifecycle triggers
4. Chose which lifecycle events you wish to use triggers upon (enrollment, revocation, expiration)
5. Select one or more existing triggers from the menu (if several are selected, they will all be called whenever the selected event occurs)
6. Click on the Save button.
From now on, whenever a selected lifecycle event will occur on the configured profile, the trigger will be called and the and the certificate will be pushed into or removed from the third party container.