New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixes #13402 allow user defined key retrieval from CYBR #13411
Fixes #13402 allow user defined key retrieval from CYBR #13411
Conversation
I verified the fix with the docker development environment. Everything works correctly except this moment: #13411 (comment) |
Tested with the empty and missing object_property key. Eveything looks good. |
NB issue #14606 created for below Using AWX 23.3.0 and trying to fetch the 'Address' via Central Credential Provider version 12.6 I encounter a key error. Please reopen this issue. How to reproduce with a Credential Type "VMware vCenter" aiming at a self managed safe:
Test button in credential edit page will show a Key Error, and playbook in debug mode using this credential in debug mode fails with this message:
|
SUMMARY
An enhancement request was made for the CyberArk Central Credential Provider Lookup to support user-defined key retrieval instead of the hardcoded
Content
retrieval which equates to a password or key value. This would allow users to specify other values to use, such as Username, Address, Port, Database, etc.This PR adds a string field to the CyberArk Central Credential Provider Lookup credential plugin metadata for
Object Property
to be defined by the user. If no value is provided, the default value isContent
which falls in line with behavior prior to this PR.related #13402
related #5743
ISSUE TYPE
COMPONENT NAME
AWX VERSION
ADDITIONAL INFORMATION
Screenshots from testing: