You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
thrownewException($"Error inserting certificate {alias}. New alias {newAlias} already exists, so certificate {alias} that is bound to one or more objects, cannot be replaced and rebound. Please remove {newAlias}, and try again.");
logger.LogDebug($"Update binding for path/name/attribute {existingUsing.path}/{existingUsing.name}/{existingUsing.attribute} for new alias {newAlias}");
thrownewException($"Certificate {alias} already exists, but overwrite is set to false. Try rescheduling job with overwrite set to true if you wish to replace this certificate.");
215
+
240
216
//no overwrite so we just try to insert
241
-
logger.LogDebug("Inserting certificate with alias: "+alias);
Copy file name to clipboardExpand all lines: README.md
+7-3Lines changed: 7 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,23 +34,25 @@
34
34
The Fortigate Orchestrator Extension supports the following use cases:
35
35
1. Inventory of local user and factory cerificates
36
36
2. Ability to add new local certificates
37
-
3. Ability to renew **unbound** local user certificates
37
+
3. Ability to replace bound* and unbound local user certificates (usually after renewal in Keyfactor Command)
38
38
4. Ability to delete **unbound** local user certificates
39
39
40
40
The Fortigate Orchestrator Extension DOES NOT support the following use cases:
41
41
1. The renewal or removal of certificates enrolled through the internal Fortigate CA
42
42
2. The renewal or removal of factory certificates
43
-
3. The renewal or removal of ANY certificate bound to a Fortigate object
43
+
3. The removal of ANY certificate bound to a Fortigate object
44
44
4. Certificate enrollment using the internal Fortigate CA (Keyfactor's "reenrollment" or "on device key generation" use case)
45
45
46
+
\* Because the Fortigate API does not allow for updating certificates in place, and to avoid temporary outages, when replacing local certificates that are bound, it is necessary to create a new name (alias) for the certificate. The new name is created using the first 8 characters of the previous name (larger names truncated due to Fortigate name length constraints) allong with a suffix comprised of "--" and a 15 character hash of the current date/time. The replaced certificate with the old name is then removed from the Fortigate instance. For example, a bound certificate with the name "CertName" would be replaced and the name would then be "CertName--8DD76A97A98E4C1". The existing bindings would remain in place with the new name. At no point during the management job would any of the bound objects be left without a valid certificate binding.
47
+
46
48
47
49
48
50
## Compatibility
49
51
50
52
This integration is compatible with Keyfactor Universal Orchestrator version 10.1 and later.
51
53
52
54
## Support
53
-
The Fortigate Universal Orchestrator extension is open source and community supported, meaning that there is **no SLA** applicable.
55
+
The Fortigate Universal Orchestrator extension is open source and there is **no SLA**. Keyfactor will address issues as resources become available. Keyfactor customers may request escalation by opening up a support ticket through their Keyfactor representative.
54
56
55
57
> To report a problem or suggest a new feature, use the **[Issues](../../issues)** tab. If you want to contribute actual bug fixes or proposed enhancements, use the **[Pull requests](../../pulls)** tab.
56
58
@@ -112,6 +114,8 @@ To use the Fortigate Universal Orchestrator extension, you **must** create the F
> For Keyfactor **Command versions 24.4 and later**, a Certificate Format dropdown is available with PFX and PEM options. Ensure that **PFX** is selected, as this determines the format of new and renewed certificates sent to the Orchestrator during a Management job. Currently, all Keyfactor-supported Orchestrator extensions support only PFX.
118
+
115
119
#### Custom Fields Tab
116
120
Custom fields operate at the certificate store level and are used to control how the orchestrator connects to the remote target server containing the certificate store to be managed. The following custom fields should be added to the store type:
Copy file name to clipboardExpand all lines: docsource/content.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,15 +3,17 @@
3
3
The Fortigate Orchestrator Extension supports the following use cases:
4
4
1. Inventory of local user and factory cerificates
5
5
2. Ability to add new local certificates
6
-
3. Ability to renew **unbound** local user certificates
6
+
3. Ability to replace bound* and unbound local user certificates (usually after renewal in Keyfactor Command)
7
7
4. Ability to delete **unbound** local user certificates
8
8
9
9
The Fortigate Orchestrator Extension DOES NOT support the following use cases:
10
10
1. The renewal or removal of certificates enrolled through the internal Fortigate CA
11
11
2. The renewal or removal of factory certificates
12
-
3. The renewal or removal of ANY certificate bound to a Fortigate object
12
+
3. The removal of ANY certificate bound to a Fortigate object
13
13
4. Certificate enrollment using the internal Fortigate CA (Keyfactor's "reenrollment" or "on device key generation" use case)
14
14
15
+
\* Because the Fortigate API does not allow for updating certificates in place, and to avoid temporary outages, when replacing local certificates that are bound, it is necessary to create a new name (alias) for the certificate. The new name is created using the first 8 characters of the previous name (larger names truncated due to Fortigate name length constraints) allong with a suffix comprised of "--" and a 15 character hash of the current date/time. The replaced certificate with the old name is then removed from the Fortigate instance. For example, a bound certificate with the name "CertName" would be replaced and the name would then be "CertName--8DD76A97A98E4C1". The existing bindings would remain in place with the new name. At no point during the management job would any of the bound objects be left without a valid certificate binding.
0 commit comments