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
+13-5Lines changed: 13 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ Keyfactor supports the retrieval of credentials from 3rd party Privileged Access
12
12
13
13
## Support for CyberArk PAM Provider
14
14
15
-
CyberArk PAM Provider is supported by Keyfactor for Keyfactor customers. If you have a support issue, please open a support ticket with your Keyfactor representative.
15
+
CyberArk PAM Provider 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
16
17
17
###### 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.
18
18
@@ -79,6 +79,7 @@ Certificate Authentication cannot be required. This may necessitate creating a S
79
79
80
80
#### For SDK-based local Credential Provider
81
81
To use a local Credential Provider instead, the Credential Provider will need to be installed on the machine that is using the PAM Provider. After installing the Credential Provider, copy the `NetStandardPasswordSDK.dll` assembly from the install location into the PAM Provider install location. This dll __needs__ to be adjacent to `cyberark-credentialprovider-pam.dll` to be properly loaded.
82
+
__Important__: When running the SDK Credential Provider on Keyfactor Command, the `NetPasswordSDK.dll` needs to be copied instead of `NetStandardPasswordSDK.dll`. This library is compatible with .NET Framework which is necessary to work in Keyfactor Command.
82
83
83
84
After registering the Credential Provider during install, make sure the Provider for the machine has been granted permission to access the Safe, as well as the Application ID that will be used.
84
85
@@ -92,7 +93,7 @@ A <code>manifest.json</code> file is included in the release. This file needs to
@@ -116,10 +117,10 @@ This file then needs to be edited to enter in the "initialization" parameters fo
116
117
117
118
#### Usage with the Keyfactor Universal Orchestrator
118
119
To use the PAM Provider to resolve a field, for example a Server Password, instead of entering in the actual value for the Server Password, enter a `json` object with the parameters specifying the field.
119
-
The parameters needed are the "instance" parameters above:
120
+
The parameters needed are the "instance" parameters above (with appropriate characters escaped for correct JSON formatting):
Copy file name to clipboardExpand all lines: readme-src/readme-config.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,7 @@ Certificate Authentication cannot be required. This may necessitate creating a S
6
6
7
7
#### For SDK-based local Credential Provider
8
8
To use a local Credential Provider instead, the Credential Provider will need to be installed on the machine that is using the PAM Provider. After installing the Credential Provider, copy the `NetStandardPasswordSDK.dll` assembly from the install location into the PAM Provider install location. This dll __needs__ to be adjacent to `cyberark-credentialprovider-pam.dll` to be properly loaded.
9
+
__Important__: When running the SDK Credential Provider on Keyfactor Command, the `NetPasswordSDK.dll` needs to be copied instead of `NetStandardPasswordSDK.dll`. This library is compatible with .NET Framework which is necessary to work in Keyfactor Command.
9
10
10
11
After registering the Credential Provider during install, make sure the Provider for the machine has been granted permission to access the Safe, as well as the Application ID that will be used.
11
12
@@ -19,7 +20,7 @@ A <code>manifest.json</code> file is included in the release. This file needs to
@@ -43,10 +44,10 @@ This file then needs to be edited to enter in the "initialization" parameters fo
43
44
44
45
#### Usage with the Keyfactor Universal Orchestrator
45
46
To use the PAM Provider to resolve a field, for example a Server Password, instead of entering in the actual value for the Server Password, enter a `json` object with the parameters specifying the field.
46
-
The parameters needed are the "instance" parameters above:
47
+
The parameters needed are the "instance" parameters above (with appropriate characters escaped for correct JSON formatting):
0 commit comments