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
+14-9Lines changed: 14 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,16 +6,18 @@ The Remote File Orchestrator allows for the remote management of file-based cert
6
6
7
7
## About the Keyfactor Universal Orchestrator Capability
8
8
9
-
This repository contains a Universal Orchestrator Extension which is a plugin to the Keyfactor Universal Orchestrator. Within the Keyfactor Platform, Orchestrators are used to manage “certificate stores” — collections of certificates and roots of trust that are found within and used by various applications.
9
+
This repository contains a Universal Orchestrator Capability which is a plugin to the Keyfactor Universal Orchestrator. Within the Keyfactor Platform, Orchestrators are used to manage “certificate stores” — collections of certificates and roots of trust that are found within and used by various applications.
10
10
11
11
The Universal Orchestrator is part of the Keyfactor software distribution and is available via the Keyfactor customer portal. For general instructions on installing Capabilities, see the “Keyfactor Command Orchestrator Installation and Configuration Guide” section of the Keyfactor documentation. For configuration details of this specific Capability, see below in this readme.
12
12
13
13
The Universal Orchestrator is the successor to the Windows Orchestrator. This Capability plugin only works with the Universal Orchestrator and does not work with the Windows Orchestrator.
14
14
15
-
---
16
15
17
16
18
17
18
+
---
19
+
20
+
19
21
20
22
## Platform Specific Notes
21
23
@@ -33,7 +35,8 @@ The Keyfactor Universal Orchestrator may be installed on either Windows or Linux
33
35
34
36
---
35
37
36
-
<!-- add integration specific information below -->
38
+
39
+
<!-- add integration specific information below -->
37
40
## Overview
38
41
The Remote File Orchestrator Extension is a multi-purpose integration that can remotely manage a variety of file-based certificate stores and can easily be extended to manage others. The certificate store types that can be managed in the current version are:
39
42
- Java Keystores of type JKS
@@ -54,12 +57,12 @@ This orchestrator extension makes use of an SSH connection to communicate remote
54
57
55
58
## Versioning
56
59
57
-
The version number of a the Remote File Orchestrator Extension can be verified by right clicking on the n the Extensions/RemoteFile installation folder, selecting Properties, and then clicking on the Details tab.
60
+
The version number of a the Remote File Orchestrator Extension can be verified by right clicking on the RemoteFile.dll file in the Extensions/RemoteFile installation folder, selecting Properties, and then clicking on the Details tab.
58
61
59
62
60
63
## Keyfactor Version Supported
61
64
62
-
The Remote File Orchestrator Extension has been tested against Keyfactor Universal Orchestrator version 9.5, but should work against earlier or later versions of the Keyfactor Universal Orchestrator.
65
+
The Remote File Orchestrator Extension has been tested against Keyfactor Universal Orchestrator version 9.9, but should work against earlier or later versions of the Keyfactor Universal Orchestrator.
63
66
64
67
65
68
## Security Considerations
@@ -80,6 +83,8 @@ The Remote File Orchestrator Extension has been tested against Keyfactor Univers
80
83
81
84
2. When creating/configuring a certificate store in Keyfactor Command, you will see a "Change Credentials" link after entering in the destination client machine (IP or DNS). This link **must** be clicked on to present the credentials dialog. However, it is not required that you enter separate credentials. Simply click SAVE in the resulting dialog without entering in credentials to use the credentials that the Keyfactor Orchestrator Service is running under. Alternatively, you may enter separate credentials into this dialog and use those to connect to the orchestrated server.
82
85
86
+
Please consult with your company's system administrator for more information on configuring SSH/SFTP/SCP or WinRM in your environment.
87
+
83
88
**SSH Key-Based Authentiation**
84
89
1. When creating a Keyfactor certificate store for the remote file orchestrator extension (see "Creating Certificate Stores" later in this README, you may supply either a user id and password for the certificate store credentials (directly or through one of Keyfactor Command's PAM integrations), or a user id and SSH private key. Both PKCS#1 (BEGIN RSA PRIVATE KEY) and PKCS#8 (BEGIN PRIVATE KEY) formats are supported for the SSH private key. If using the normal Keyfactor Command credentials dialog without PAM integration, just copy and paste the full SSH private key into the Password textbox.
85
90
@@ -171,7 +176,7 @@ Entry Parameters Tab:
171
176
- no additional entry parameters
172
177
173
178
174
-
CURL script to automate certificate store type creation can be found [here](https://github.com/Keyfactor/remote-file-orchestrator/blob/initial-version/Certificate%20Store%20Type%20CURL%20Scripts/PKCS12.curl)
179
+
CURL script to automate certificate store type creation can be found [here](Certificate%20Store%20Type%20CURL%20Scripts/PKCS12.curl)
175
180
176
181
177
182
@@ -201,7 +206,7 @@ Entry Parameters Tab:
201
206
- no additional entry parameters
202
207
203
208
204
-
CURL script to automate certificate store type creation can be found [here](https://github.com/Keyfactor/remote-file-orchestrator/blob/initial-version/Certificate%20Store%20Type%20CURL%20Scripts/JKS.curl)
209
+
CURL script to automate certificate store type creation can be found [here](Certificate%20Store%20Type%20CURL%20Scripts/JKS.curl)
205
210
206
211
207
212
@@ -235,7 +240,7 @@ Entry Parameters Tab:
235
240
- no additional entry parameters
236
241
237
242
238
-
CURL script to automate certificate store type creation can be found [here](https://github.com/Keyfactor/remote-file-orchestrator/blob/initial-version/Certificate%20Store%20Type%20CURL%20Scripts/PEM.curl)
243
+
CURL script to automate certificate store type creation can be found [here](Certificate%20Store%20Type%20CURL%20Scripts/PEM.curl)
239
244
240
245
241
246
@@ -265,7 +270,7 @@ Entry Parameters Tab:
265
270
- no additional entry parameters
266
271
267
272
268
-
CURL script to automate certificate store type creation can be found [here](https://github.com/Keyfactor/remote-file-orchestrator/blob/initial-version/Certificate%20Store%20Type%20CURL%20Scripts/KDB.curl)
273
+
CURL script to automate certificate store type creation can be found [here](Certificate%20Store%20Type%20CURL%20Scripts/KDB.curl)
thrownewRemoteFileException($"Error making a SSH connection to remote server {Connection.Host}, for user {Connection.Username}. Please contact your company's system administrator to verify connection and permission settings.",ex);
_logger.LogDebug($"SCP upload failed. Attempting with SFTP protocol...");
165
172
else
166
-
throwex;
173
+
thrownewRemoteFileException("Error attempting SCP file transfer to {Connection.Host} using login {Connection.Username} and connection method {Connection.AuthenticationMethods[0].Name}. Please contact your company's system administrator to verify connection and permission settings.",ex);
thrownewRemoteFileException("Error attempting SFTP file transfer to {Connection.Host} using login {Connection.Username} and connection method {Connection.AuthenticationMethods[0].Name}. Please contact your company's system administrator to verify connection and permission settings.",ex);
194
201
}
195
202
finally
196
203
{
@@ -235,7 +242,7 @@ public override byte[] DownloadCertificateFile(string path)
235
242
{
236
243
try
237
244
{
238
-
_logger.LogDebug($"SCP connection attempt to{Connection.Host} using login {Connection.Username} and connection method {Connection.AuthenticationMethods[0].Name}");
245
+
_logger.LogDebug($"SCP connection attempt from{Connection.Host} using login {Connection.Username} and connection method {Connection.AuthenticationMethods[0].Name}");
239
246
client.Connect();
240
247
241
248
using(MemoryStreamstream=newMemoryStream())
@@ -252,7 +259,7 @@ public override byte[] DownloadCertificateFile(string path)
_logger.LogDebug($"SCP download failed. Attempting with SFTP protocol...");
254
261
else
255
-
throwex;
262
+
thrownewRemoteFileException($"Error attempting SCP file transfer from {Connection.Host} using login {Connection.Username} and connection method {Connection.AuthenticationMethods[0].Name}. Please contact your company's system administrator to verify connection and permission settings.",ex);
256
263
}
257
264
finally
258
265
{
@@ -267,7 +274,7 @@ public override byte[] DownloadCertificateFile(string path)
267
274
{
268
275
try
269
276
{
270
-
_logger.LogDebug($"SFTP connection attempt to{Connection.Host} using login {Connection.Username} and connection method {Connection.AuthenticationMethods[0].Name}");
277
+
_logger.LogDebug($"SFTP connection attempt from{Connection.Host} using login {Connection.Username} and connection method {Connection.AuthenticationMethods[0].Name}");
271
278
client.Connect();
272
279
273
280
using(MemoryStreamstream=newMemoryStream())
@@ -280,7 +287,7 @@ public override byte[] DownloadCertificateFile(string path)
280
287
{
281
288
_logger.LogError("Exception during SFTP download...");
thrownewRemoteFileException($"Error attempting SFTP file transfer from {Connection.Host} using login {Connection.Username} and connection method {Connection.AuthenticationMethods[0].Name}. Please contact your company's system administrator to verify connection and permission settings.",ex);
Copy file name to clipboardExpand all lines: readme_source.md
+9-7Lines changed: 9 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
<!-- add integration specific information below -->
1
+
<!-- add integration specific information below -->
2
2
## Overview
3
3
The Remote File Orchestrator Extension is a multi-purpose integration that can remotely manage a variety of file-based certificate stores and can easily be extended to manage others. The certificate store types that can be managed in the current version are:
4
4
- Java Keystores of type JKS
@@ -19,12 +19,12 @@ This orchestrator extension makes use of an SSH connection to communicate remote
19
19
20
20
## Versioning
21
21
22
-
The version number of a the Remote File Orchestrator Extension can be verified by right clicking on the n the Extensions/RemoteFile installation folder, selecting Properties, and then clicking on the Details tab.
22
+
The version number of a the Remote File Orchestrator Extension can be verified by right clicking on the RemoteFile.dll file in the Extensions/RemoteFile installation folder, selecting Properties, and then clicking on the Details tab.
23
23
24
24
25
25
## Keyfactor Version Supported
26
26
27
-
The Remote File Orchestrator Extension has been tested against Keyfactor Universal Orchestrator version 9.5, but should work against earlier or later versions of the Keyfactor Universal Orchestrator.
27
+
The Remote File Orchestrator Extension has been tested against Keyfactor Universal Orchestrator version 9.9, but should work against earlier or later versions of the Keyfactor Universal Orchestrator.
28
28
29
29
30
30
## Security Considerations
@@ -45,6 +45,8 @@ The Remote File Orchestrator Extension has been tested against Keyfactor Univers
45
45
46
46
2. When creating/configuring a certificate store in Keyfactor Command, you will see a "Change Credentials" link after entering in the destination client machine (IP or DNS). This link **must** be clicked on to present the credentials dialog. However, it is not required that you enter separate credentials. Simply click SAVE in the resulting dialog without entering in credentials to use the credentials that the Keyfactor Orchestrator Service is running under. Alternatively, you may enter separate credentials into this dialog and use those to connect to the orchestrated server.
47
47
48
+
Please consult with your company's system administrator for more information on configuring SSH/SFTP/SCP or WinRM in your environment.
49
+
48
50
**SSH Key-Based Authentiation**
49
51
1. When creating a Keyfactor certificate store for the remote file orchestrator extension (see "Creating Certificate Stores" later in this README, you may supply either a user id and password for the certificate store credentials (directly or through one of Keyfactor Command's PAM integrations), or a user id and SSH private key. Both PKCS#1 (BEGIN RSA PRIVATE KEY) and PKCS#8 (BEGIN PRIVATE KEY) formats are supported for the SSH private key. If using the normal Keyfactor Command credentials dialog without PAM integration, just copy and paste the full SSH private key into the Password textbox.
50
52
@@ -136,7 +138,7 @@ Entry Parameters Tab:
136
138
- no additional entry parameters
137
139
138
140
139
-
CURL script to automate certificate store type creation can be found [here](https://github.com/Keyfactor/remote-file-orchestrator/blob/initial-version/Certificate%20Store%20Type%20CURL%20Scripts/PKCS12.curl)
141
+
CURL script to automate certificate store type creation can be found [here](Certificate%20Store%20Type%20CURL%20Scripts/PKCS12.curl)
140
142
141
143
142
144
@@ -166,7 +168,7 @@ Entry Parameters Tab:
166
168
- no additional entry parameters
167
169
168
170
169
-
CURL script to automate certificate store type creation can be found [here](https://github.com/Keyfactor/remote-file-orchestrator/blob/initial-version/Certificate%20Store%20Type%20CURL%20Scripts/JKS.curl)
171
+
CURL script to automate certificate store type creation can be found [here](Certificate%20Store%20Type%20CURL%20Scripts/JKS.curl)
170
172
171
173
172
174
@@ -200,7 +202,7 @@ Entry Parameters Tab:
200
202
- no additional entry parameters
201
203
202
204
203
-
CURL script to automate certificate store type creation can be found [here](https://github.com/Keyfactor/remote-file-orchestrator/blob/initial-version/Certificate%20Store%20Type%20CURL%20Scripts/PEM.curl)
205
+
CURL script to automate certificate store type creation can be found [here](Certificate%20Store%20Type%20CURL%20Scripts/PEM.curl)
204
206
205
207
206
208
@@ -230,7 +232,7 @@ Entry Parameters Tab:
230
232
- no additional entry parameters
231
233
232
234
233
-
CURL script to automate certificate store type creation can be found [here](https://github.com/Keyfactor/remote-file-orchestrator/blob/initial-version/Certificate%20Store%20Type%20CURL%20Scripts/KDB.curl)
235
+
CURL script to automate certificate store type creation can be found [here](Certificate%20Store%20Type%20CURL%20Scripts/KDB.curl)
0 commit comments