-
Notifications
You must be signed in to change notification settings - Fork 0
Merge 1.4.0 to main #14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -31,17 +31,18 @@ | |||||
|
|
||||||
| ## Overview | ||||||
|
|
||||||
| The Fortigate Orchestrator Extension supports the following use cases: | ||||||
| 1. Inventory of local user and factory cerificates | ||||||
| 2. Ability to add new local certificates | ||||||
| 3. Ability to replace bound* and unbound local user certificates (usually after renewal in Keyfactor Command) | ||||||
| 4. Ability to delete **unbound** local user certificates | ||||||
| The Fortigate Orchestrator Extension supports the following use cases against a specified VDOM: | ||||||
| 1. Inventory of local user and factory VDOM and globally scoped cerificates | ||||||
|
||||||
| 1. Inventory of local user and factory VDOM and globally scoped cerificates | |
| 1. Inventory of local user and factory VDOM and globally scoped certificates |
Copilot
AI
Jan 8, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The sentence is grammatically incomplete. It should read "determine which asset should be downloaded" instead of "determine the asset should be downloaded".
| Navigate to the [Fortigate Universal Orchestrator extension GitHub version page](https://github.com/Keyfactor/fortigate-orchestrator/releases/latest). Refer to the compatibility matrix below to determine the asset should be downloaded. Then, click the corresponding asset to download the zip archive. | |
| Navigate to the [Fortigate Universal Orchestrator extension GitHub version page](https://github.com/Keyfactor/fortigate-orchestrator/releases/latest). Refer to the compatibility matrix below to determine which asset should be downloaded. Then, click the corresponding asset to download the zip archive. |
Copilot
AI
Jan 8, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This row appears to be a duplicate documentation entry. The table already has an "Orchestrator" row at line 241 with identical content. This duplicate entry is placed where "Store Path" documentation should be, causing confusion about the VDOM configuration requirement.
| | Orchestrator | Select an approved orchestrator capable of managing `Fortigate` certificates. Specifically, one with the `Fortigate` capability. | | |
| | Store Path | For Fortigate VDOM configurations, enter the VDOM name or path required by your deployment. For non‑VDOM configurations, leave this blank or use the default path as appropriate. | |
Copilot
AI
Jan 8, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This row appears to be a duplicate documentation entry. The table already has an "Orchestrator" row at line 267 with identical content. This duplicate entry is placed where "Store Path" documentation should be, causing confusion about the VDOM configuration requirement.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This import statement for
Org.BouncyCastle.Tlsappears to be unused in the code. No types from this namespace are referenced in the visible changes to this file.