|
1 | | -# digicert-certcentral-anycagateway |
2 | 1 |
|
3 | | -DigiCert CertCentral plugin for the AnyCA Gateway framework |
| 2 | +# DigiCert CertCentral AnyCA REST Gateway Plugin |
4 | 3 |
|
5 | | -#### Integration status: Prototype - Demonstration quality. Not for use in customer environments. |
| 4 | +DigiCert CertCentral plugin for the AnyCA REST Gateway framework |
6 | 5 |
|
| 6 | +#### Integration status: Production - Ready for use in production environments. |
7 | 7 |
|
8 | | -## About the Keyfactor AnyGateway CA Connector |
| 8 | +## About the Keyfactor |
9 | 9 |
|
10 | | -This repository contains an AnyGateway CA Connector, which is a plugin to the Keyfactor AnyGateway. AnyGateway CA Connectors allow Keyfactor Command to be used for inventory, issuance, and revocation of certificates from a third-party certificate authority. |
11 | 10 |
|
12 | 11 |
|
| 12 | +## Support for DigiCert CertCentral AnyCA REST Gateway Plugin |
13 | 13 |
|
14 | | - |
15 | | -## Support for digicert-certcentral-anycagateway |
16 | | - |
17 | | -digicert-certcentral-anycagateway is open source and community supported, meaning that there is **no SLA** applicable for these tools. |
| 14 | +DigiCert CertCentral AnyCA REST Gateway Plugin 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 |
18 | 15 |
|
19 | 16 | ###### 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. |
20 | 17 |
|
| 18 | +--- |
21 | 19 |
|
22 | 20 |
|
23 | 21 | --- |
24 | 22 |
|
25 | 23 |
|
26 | 24 |
|
| 25 | + |
| 26 | +# Introduction |
27 | 27 |
|
| 28 | +This AnyCA REST Gateway plug-in enables issuance, revocation, and synchronization of certificates from DigiCert's CertCentral offering. |
| 29 | +# Prerequisites |
28 | 30 |
|
| 31 | +## Prerequisite: Certificate Chain |
29 | 32 |
|
30 | | -## Keyfactor AnyGateway Framework Supported |
| 33 | +In order to request certificates from the Keyfactor AnyGateway, the Keyfactor Command server must trust the certificate chain of trust. To ensure trust is established, download your Root and/or Subordinate CA certificates from DigiCert and import them into the appropriate local certificate stores on the Keyfactor AnyGateway and Command servers. More information can be found in the [AnyCA Gateway REST Install Guide](https://software.keyfactor.com/Guides/AnyCAGatewayREST/Content/AnyCAGatewayREST/Preparing.htm) |
31 | 34 |
|
32 | | -This gateway was compiled against version 1.0.0 of the AnyGateway Framework. You will need at least this version of the AnyGateway Framework Installed. If you have a later AnyGateway Framework Installed you will probably need to add binding redirects in the CAProxyServer.exe.config file to make things work properly. |
| 35 | +## Installation |
| 36 | +1. Download latest successful build from [GitHub Releases](../../releases/latest) |
33 | 37 |
|
| 38 | +2. Extract the .zip file, and from it, copy DigicertCAPlugin.dll and DigicertCAPlugin.deps.json to the 'C:\Program Files\Keyfactor\AnyCA Gateway\AnyGatewayREST\net6.0\Extensions' directory |
34 | 39 |
|
| 40 | +3. Within the 'C:\Program Files\Keyfactor\AnyCA Gateway\AnyGatewayREST\net6.0\Extensions\Connectors' folder, update the manifest.json file to contain the following: |
35 | 41 |
|
36 | | ---- |
| 42 | +```json |
| 43 | +{ |
| 44 | + "extensions": { |
| 45 | + "Keyfactor.AnyGateway.Extensions.IAnyCAPlugin": { |
| 46 | + "CertCentralCAPlugin": { |
| 47 | + "assemblypath": "../DigicertCAPlugin.dll", |
| 48 | + "TypeFullName": "Keyfactor.Extensions.CAPlugin.DigiCert.CertCentralCAPlugin" |
| 49 | + } |
| 50 | + } |
| 51 | + } |
| 52 | +} |
| 53 | +``` |
37 | 54 |
|
| 55 | +NOTE: If the Connectors folder and/or the manifest.json file do not exist, they must be manually created |
38 | 56 |
|
39 | | -# Introduction |
40 | | -This AnyGateway plug-in enables issuance, revocation, and synchronization of certificates from DigiCert's CertCentral offering. |
41 | | -# Prerequisites |
| 57 | +4. Restart the AnyCA Gateway service |
42 | 58 |
|
43 | | -## Certificate Chain |
| 59 | +5. Navigate to the AnyCA Gateway REST portal and verify that the Gateway recognizes the DigiCert plugin by hovering over the ⓘ symbol to the right of the Gateway on the top left of the portal. CAPlugin Type should now be listed as CertCentralCA. |
44 | 60 |
|
45 | | -In order to enroll for certificates the Keyfactor Command server must trust the trust chain. Once you create your Root and/or Subordinate CA, make sure to import the certificate chain into the AnyGateway and Command Server certificate store |
46 | 61 |
|
| 62 | +## Configuration |
47 | 63 |
|
48 | | -# Install |
49 | | -* Download latest successful build from [GitHub Releases](../../releases/latest) |
| 64 | +1. Follow the [official Keyfactor AnyCA Gateway REST documentation](https://software.keyfactor.com/Guides/AnyCAGatewayREST/Content/AnyCAGatewayREST/AddCA-Gateway.htm#Add_or_Edit_a_Certificate_Authority) to define a new Certificate Authority, using the following information to configure the CA Connection section: |
50 | 65 |
|
51 | | -* Copy DigiCertCAGateway.dll and DigiCertCAGateway.deps.json to the Program Files\Keyfactor\AnyCA Gateway\AnyGatewayREST\net6.0\Extensions directory |
| 66 | +SETTING | REQUIRED? | DESCRIPTION |
| 67 | +--|--|-- |
| 68 | +Enabled | Yes | Enables the DigiCert gateway functionality. Should almost always be set to 'true' |
| 69 | +APIKey | Yes | The API key the Gateway should use to communicate with the DigiCert API. Can be generated from the DigiCert portal. |
| 70 | +Region | No | The geographic region associated with your DigiCert account. Valid values are US and EU. Default if not provided is US. |
| 71 | +DivisionId | No | If your CertCentral account has multiple divisions AND uses any custom per-division product settings, provide a division ID for the gateway to use for product type lookups. |
| 72 | +RevokeCertificateOnly | No | If set to 'true', revoke operations will only revoke the individual certificate in question rather than the entire DigiCert order. Default if not provided is 'false'. |
| 73 | +SyncCAFilter | No | If you list one or more DigiCert issuing CA IDs here (comma-separated if more than one), the sync process will only return certs issued by one of those CAs. Leave this option empty to sync all certs from all CAs. |
| 74 | +FilterExpiredOrders | No | If set to 'true', syncing will not return certs that are expired more than a specified number of days. The number of days is specified by the SyncExpirationDays config option. Default value is 'false'. |
| 75 | +SyncExpirationDays | No | Only used if FilterExpiredOrders is 'true', otherwise ignored. Sets the number of days a cert has to be expired for the sync process to no longer sync it. For example, a value of 30 means sync will continue to return certs that have expired within the past 30 days, but not ones older than that. Default value is 0, meaning sync would not return any certs expired before the current day. |
| 76 | + |
| 77 | +2. After saving the CA configuration, Follow the [official AnyCA Gateway REST documentation](https://software.keyfactor.com/Guides/AnyCAGatewayREST/Content/AnyCAGatewayREST/AddCP-Gateway.htm#Certificate_Profile) to define one or more Certificate Profiles. |
| 78 | +3. Edit your newly configured CA, and you should now be able to modify the Templates tab. You need at least one template for each product type you wish to be able to enroll for. It is recommended to include the product type in the template name to make them easier to identify. Use the following information to configure the parameters for each template: |
| 79 | + |
| 80 | +SETTING | REQUIRED? | DESCRIPTION |
| 81 | +--|--|-- |
| 82 | +LifetimeDays | No | The number of days of validity to use when requesting certs. Default if not provided is 365. NOTE FOR RENEWALS: If the value of LifetimeDays is evenly divisible by 365, the expiration day and month of the new cert will be set to the same values as the old cert if possible, to avoid renewal date drift. |
| 83 | +CACertId | No | The ID of the issuing CA to be used by DigiCert. If not specified, the default for your account will be used. |
| 84 | +Organization-Name | No | If specified, this value will override any organization name provided in the subject of the cert request on enrollment. Useful for requests (such as ACME) that contain no subject. |
| 85 | +RenewalWindowDays | No | The number of days from expiration that the gateway should do a reissue rather than a renewal. Default if not provided is 90, meaning any renewal request for certs that expire in more than 90 days will be treated as a reissue request. |
52 | 86 |
|
53 | | -* Update the manifest.json file located in Program Files\Keyfactor\AnyCA Gateway\AnyGatewayREST\net6.0\Extensions\Connectors |
54 | | - * If the manifest.json file or the Connectors folder do not exist, create them. |
55 | | - ```json |
56 | | -{ |
57 | | - "extensions": { |
58 | | - "Keyfactor.AnyGateway.Extensions.ICAConnector": { |
59 | | - "DigiCertCAConnector": { |
60 | | - "assemblypath": "../DigiCertCAGateway.dll", |
61 | | - "TypeFullName": "Keyfactor.Extensions.CAGateway.DigiCert.CertCentralCAConnector" |
62 | | - } |
63 | | - } |
64 | | - } |
65 | | -} |
66 | | - ``` |
67 | 87 |
|
0 commit comments