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
Copy file name to clipboardExpand all lines: README.md
+6-17Lines changed: 6 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,9 +4,7 @@ A tool to automatically synchronize metadata fields and their content from DigiC
4
4
5
5
#### Integration status: Production - Ready for use in production environments.
6
6
7
-
## About the Keyfactor API Client
8
7
9
-
This API client allows for programmatic management of Keyfactor resources.
10
8
11
9
12
10
@@ -19,30 +17,19 @@ Digicert Metadata Sync is open source and there is **no SLA** for this tool/libr
19
17
20
18
21
19
22
-
23
-
24
20
## Overview
25
-
This tool primarily sets up metadata fields in Keyfactor for the custom metadata fields in DigiCert, which are named as such, but can also setup metadata fields in Keyfactor for non-custom fields available in DigiCert and unavailable in Keyfactor by default, such as the Digicert Cert ID and the Organization contact. These fields are referred to as manual fields in the context of this tool. After setting up these fields, the tool proceeds to update the contents of these fields. This tool only adds metadata to certificates that have already been imported into Keyfactor. Additionally, this tool requires a properly installed and functioning AnyGateway configured to work with Keyfactor and Digicert. The latest update allows for syncronization of custom field contents from Keyfactor to DigiCert. New fields are created in Keyfactor and DigiCert to accomodate for this.
21
+
This tool primarily sets up metadata fields in Keyfactor for the custom metadata fields in DigiCert, which are named as such, but can also setup metadata fields in Keyfactor for non-custom fields available in DigiCert and unavailable in Keyfactor by default, such as the Digicert Cert ID and the Organization contact. These fields are referred to as manual fields in the context of this tool. After setting up these fields, the tool proceeds to update the contents of these fields. This tool only adds metadata to certificates that have already been imported into Keyfactor. Additionally, this tool requires a properly installed and functioning AnyGateway configured to work with Keyfactor and Digicert.
26
22
27
23
## Installation and Usage
28
-
The tool comes as a Windows executable. The tool performs synchronization each time its run. For the tool to run automatically, it needs to be added as a scheduled process using Windows. The advised interval for running it is once per week. The files App.config and manualfields.json need to be present in the same directory as the tool for it to run correctly. The specific location from which the tool is ran does not matter, but it needs to have access to both the Keyfactor API endpoint as well as Digicert, and appropriate permissions for access to the configuration files.
24
+
The tool comes as a Windows executable. The tool performs synchronization each time its run. For the tool to run automatically, it needs to be added as a scheduled process using Windows. The advised interval for running it is once per week. The files DigicertMetadataSync.dll.config and manualfields.json need to be present in the same directory as the tool for it to run correctly. The specific location from which the tool is ran does not matter, but it needs to have access to both the Keyfactor API endpoint as well as Digicert, and appropriate permissions for access to the configuration files.
29
25
An explanation for the settings found in these files is given below.
30
26
31
-
## Command Line Arguments
32
-
One of these two arguments needs to be used for the tool to run.
33
-
- <b>"kftodc"</b>
34
-
Syncronizes the contents of custom fields listed in manualfields.json from Keyfactor to DigiCert. If the fields in manualfields.json do not exist in Keyfactor or DigiCert, they are created first. Example: ```.\DigicertMetadataSync.exe kftodc```
35
-
- <b>"dctokf"</b>
36
-
Syncronizes the contents of both custom and non-custom fields from DigiCert to Keyfactor. The fields are listed in manualfields.json, and are created if necessary.
37
-
Example: ```.\DigicertMetadataSync.exe dctokf```
38
27
39
28
## Settings
40
29
The settings currently present in these files are shown as an example and need to be configured for your specific situation.
41
-
### app.config settings
30
+
### DigicertMetadataSync.dll.config settings
42
31
- <b>DigicertAPIKey</b>
43
-
Standard DigiCert API access key.
44
-
- <b>DigicertAPIKeyTopPerm</b>
45
-
DigiCert API access key with restrictions set to "None" - <b>required for sync from Keyfactor to DigiCert</b>.
32
+
Standard DigiCert API access key
46
33
- <b>KeyfactorDomainAndUser</b>
47
34
Same credential as used when logging into Keyfactor Command. A different set of credentials can be used provided they have adequate access permissions.
48
35
- <b>KeyfactorPassword</b>
@@ -86,4 +73,6 @@ String to be input into Keyfactor as the metadata field hint.
86
73
- <b>KeyfactorAllowAPI</b>
87
74
Allows API management of this metadata field in Keyfactor. Should be set to true for continuous synchronization with this tool.
88
75
76
+
### Logging
77
+
Logging functionality can be configured via entering either "Debug" or "Trace" into the value of `<variable name="minLogLevel" value="Debug" />` in NLog.config.
0 commit comments