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
+26-18Lines changed: 26 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,9 +77,9 @@ The Remote File Universal Orchestrator extension implements 6 Certificate Store
77
77
This integration is compatible with Keyfactor Universal Orchestrator version 10.4 and later.
78
78
79
79
## Support
80
-
The Remote File Universal Orchestrator extension If you have a support issue, please open a support ticket by either contacting your Keyfactor representative or via the Keyfactor Support Portal at https://support.keyfactor.com.
80
+
The Remote File Universal Orchestrator extension is supported by Keyfactor. If you require support for any issues or have feature request, please open a support ticket by either contacting your Keyfactor representative or via the Keyfactor Support Portal at https://support.keyfactor.com.
81
81
82
-
> 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.
82
+
> If you want to contribute bug fixes or additional enhancements, use the **[Pull requests](../../pulls)** tab.
83
83
84
84
## Requirements & Prerequisites
85
85
@@ -90,26 +90,34 @@ Before installing the Remote File Universal Orchestrator extension, we recommend
90
90
<summary><b>Certificate stores hosted on Linux servers:</b></summary>
91
91
92
92
1. The Remote File Orchestrator Extension makes use of a few common Linux commands when managing stores on Linux
93
-
servers. If the credentials you will be connecting with need elevated access to run these commands or to access the
93
+
servers as well as some specialized CLI commands for certain store types. If the credentials you will be connecting with
94
+
need elevated access to run these commands or to access the
94
95
certificate store files these commands operate against, you must set up the user id as a sudoer with no password
95
96
necessary and set the config.json `UseSudo` value to `Y`. When `RemoteFile` is using orchestration, managing local or
96
97
external certificate stores using `SSH` or `WinRM`, the security context is determined by the user id entered into the
97
98
Keyfactor Command certificate store or discovery job screens. When RemoteFile is running as an agent, managing local
98
99
stores only, the security context is the user id running the Keyfactor Command Universal Orchestrator service
99
-
account. The full list of these commands is below:
|`echo`| Used to append a newline and terminate all commands sent. |
104
-
|`find`| Used by Discovery jobs to locate potential certificate stores on the file system. |
105
-
|`cp`| Used by Inventory and Management Add/Remove/Create jobs to determine if certificate store file exists. |
106
-
|`ls`| Used by Management Add/Remove jobs to copy the certificate store file to a temporary file (only when an alternate download folder has been configured). |
107
-
|`chown`| Used by the Inventory and Management Add/Remove jobs to set the permissions on the temporary file (only when an alternate download folder has been configured). |
108
-
|`tee`| Used by Management Add/Remove jobs to copy the temporary uploaded certificate file to the certificate store file (only when an alternate upload folder has been configured). |
109
-
|`rm`| Used by Inventory and Management Add/Remove jobs to remove temporary files (only when an alternate upload/download folder has been configured). |
110
-
|`install`| Used by the Management Create Store job when initializing a certificate store file. |
111
-
|`orapki`| Oracle Wallet CLI utility used by Inventory and Management Add/Remove jobs to manipulate an Oracle Wallet certificate store. Used for the RFORA store type only. |
112
-
|`gskcapicmd`| IBM Key Database CLI utility used by Inventory and Management Add/Remove jobs to manipulate an IBM Key Database certificate store. Used for the RFKDB store type only. |
100
+
account. The full list of these commands and when they are used is illustrated below:
(a) - Only used if [config.json](#post-installation) setting SeparateUploadFilePath is used (non empty value)
116
+
(b) - Only used if [config.json](#post-installation) setting SeparateUploadFilePath is used (non empty value) AND the [config.json](#post-installation) or certificate store setting SudoImpersonatedUser is not used (empty value)
117
+
(c) - Only used if store type is RFKDB or RFORA AND [config.json](#post-installation) setting SeparateUploadFilePath is used (non empty value)
118
+
(d) - Only used if using store type is either RFKDB or RFORA OR any store type and the [config.json](#post-installation) setting SeparateUploadFilePath is used (non empty value)
119
+
(e) - RFORA store type only
120
+
(f) - RFKDB store type only
113
121
114
122
2. When orchestrating management of local or external certificate stores, the Remote File Orchestrator Extension makes
115
123
use of SFTP and/or SCP to transfer files to and from the orchestrated server. `SFTP/SCP` cannot make use of `sudo`, so
@@ -906,7 +914,7 @@ the Keyfactor Command Portal
906
914
907
915
## Post Installation
908
916
909
-
The Remote File Orchestrator Extension uses a JSON configuration file. It is located in the `{Keyfactor Orchestrator Installation Folder}\Extensions\RemoteFile`. None of the values are required, and a description of each follows below:
917
+
The Remote File Orchestrator Extension uses a JSON configuration file. It is located at `{Keyfactor Orchestrator Installation Folder}\Extensions\RemoteFile\config.json`. None of the values are required, and a description of each follows below:
|`echo`| Used to append a newline and terminate all commands sent. |
46
-
|`find`| Used by Discovery jobs to locate potential certificate stores on the file system. |
47
-
|`cp`| Used by Inventory and Management Add/Remove/Create jobs to determine if certificate store file exists. |
48
-
|`ls`| Used by Management Add/Remove jobs to copy the certificate store file to a temporary file (only when an alternate download folder has been configured). |
49
-
|`chown`| Used by the Inventory and Management Add/Remove jobs to set the permissions on the temporary file (only when an alternate download folder has been configured). |
50
-
|`tee`| Used by Management Add/Remove jobs to copy the temporary uploaded certificate file to the certificate store file (only when an alternate upload folder has been configured). |
51
-
|`rm`| Used by Inventory and Management Add/Remove jobs to remove temporary files (only when an alternate upload/download folder has been configured). |
52
-
|`install`| Used by the Management Create Store job when initializing a certificate store file. |
53
-
|`orapki`| Oracle Wallet CLI utility used by Inventory and Management Add/Remove jobs to manipulate an Oracle Wallet certificate store. Used for the RFORA store type only. |
54
-
|`gskcapicmd`| IBM Key Database CLI utility used by Inventory and Management Add/Remove jobs to manipulate an IBM Key Database certificate store. Used for the RFKDB store type only. |
42
+
account. The full list of these commands and when they are used is illustrated below:
(a) - Only used if [config.json](#post-installation) setting SeparateUploadFilePath is used (non empty value)
58
+
(b) - Only used if [config.json](#post-installation) setting SeparateUploadFilePath is used (non empty value) AND the [config.json](#post-installation) or certificate store setting SudoImpersonatedUser is not used (empty value)
59
+
(c) - Only used if store type is RFKDB or RFORA AND [config.json](#post-installation) setting SeparateUploadFilePath is used (non empty value)
60
+
(d) - Only used if using store type is either RFKDB or RFORA OR any store type and the [config.json](#post-installation) setting SeparateUploadFilePath is used (non empty value)
61
+
(e) - RFORA store type only
62
+
(f) - RFKDB store type only
55
63
56
64
2. When orchestrating management of local or external certificate stores, the Remote File Orchestrator Extension makes
57
65
use of SFTP and/or SCP to transfer files to and from the orchestrated server. `SFTP/SCP` cannot make use of `sudo`, so
@@ -99,7 +107,7 @@ Please consult with your system administrator for more information on configurin
99
107
100
108
## Post Installation
101
109
102
-
The Remote File Orchestrator Extension uses a JSON configuration file. It is located in the `{Keyfactor Orchestrator Installation Folder}\Extensions\RemoteFile`. None of the values are required, and a description of each follows below:
110
+
The Remote File Orchestrator Extension uses a JSON configuration file. It is located at `{Keyfactor Orchestrator Installation Folder}\Extensions\RemoteFile\config.json`. None of the values are required, and a description of each follows below:
0 commit comments