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
* Update generated README
* Fix inventory issue where a 404 on an individual managed web site would cause inventory to end returning no certificates.
* Update bootstrap and manifest
- Bug fix: Individual site timeouts will no longer end inventory but will instead skip that site and move on. Inventory in those cases will produce a warning that certificates could not be retrieved for one or more sites, but it will still return all retrieved certificates.
returnnewJobResult(){Result=Keyfactor.Orchestrators.Common.Enums.OrchestratorJobStatusJobResult.Warning,JobHistoryId=config.JobHistoryId,FailureMessage="One or more certificates could not be returned. Please see the log for more details."};
returnnewJobResult(){Result=Keyfactor.Orchestrators.Common.Enums.OrchestratorJobStatusJobResult.Warning,JobHistoryId=config.JobHistoryId,FailureMessage=$"Overwrite is set to false but there is a certificate that already is bound to {config.JobCertificate.Alias}. Please set overwrite to true and reschedule the job to replace this certificate."};
Copy file name to clipboardExpand all lines: README.md
+13-1Lines changed: 13 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,4 @@
1
+
1
2
# Imperva
2
3
3
4
The Imperva Orchestrator Extension allows for the management of SSL certificates bound to web sites managed by the Imperva cloud-based firewall.
@@ -12,18 +13,22 @@ The Universal Orchestrator is part of the Keyfactor software distribution and is
12
13
13
14
The Universal Orchestrator is the successor to the Windows Orchestrator. This Orchestrator Extension plugin only works with the Universal Orchestrator and does not work with the Windows Orchestrator.
14
15
16
+
## Support for Imperva
15
17
18
+
Imperva is supported by Keyfactor for Keyfactor customers. If you have a support issue, please open a support ticket via the Keyfactor Support Portal at https://support.keyfactor.com
16
19
20
+
###### 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.
17
21
18
22
---
19
23
20
24
25
+
---
26
+
21
27
22
28
23
29
## Keyfactor Version Supported
24
30
25
31
The minimum version of the Keyfactor Universal Orchestrator Framework needed to run this version of the extension is 10.1
26
-
27
32
## Platform Specific Notes
28
33
29
34
The Keyfactor Universal Orchestrator may be installed on either Windows or Linux based platforms. The certificate operations supported by a capability may vary based what platform the capability is installed on. The table below indicates what capabilities are supported based on which platform the encompassing Universal Orchestrator is running.
@@ -51,6 +56,11 @@ It is not necessary to use a PAM Provider for all of the secrets available above
51
56
52
57
If a PAM Provider will be used for one of the fields above, start by referencing the [Keyfactor Integration Catalog](https://keyfactor.github.io/integrations-catalog/content/pam). The GitHub repo for the PAM Provider to be used contains important information such as the format of the `json` needed. What follows is an example but does not reflect the `json` values for all PAM Providers as they have different "instance" and "initialization" parameter names and values.
To use a PAM Provider to resolve a field, in this example the __Server Password__ will be resolved by the `Hashicorp-Vault` provider, first install the PAM Provider extension from the [Keyfactor Integration Catalog](https://keyfactor.github.io/integrations-catalog/content/pam) on the Universal Orchestrator.
@@ -77,6 +87,8 @@ To have the __Server Password__ field resolved by the `Hashicorp-Vault` provider
77
87
~~~
78
88
79
89
This text would be entered in as the value for the __Server Password__, instead of entering in the actual password. The Orchestrator will attempt to use the PAM Provider to retrieve the __Server Password__. If PAM should not be used, just directly enter in the value for the field.
Copy file name to clipboardExpand all lines: integration-manifest.json
+31-2Lines changed: 31 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -4,12 +4,15 @@
4
4
"name": "Imperva",
5
5
"status": "production",
6
6
"description": "The Imperva Orchestrator Extension allows for the management of SSL certificates bound to web sites managed by the Imperva cloud-based firewall.",
0 commit comments