Skip to content
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

Custom Platform Appears to support API Key Operations but it is not documented #63

Open
aamburnArcher opened this issue Feb 24, 2025 · 0 comments

Comments

@aamburnArcher
Copy link

Hi,

Safeguard for Privileged Passwords has added support for the following API Key management tasks:

ChangeApiKey
CheckApiKey

When added to a Custom Platform Script, they are accepted as Platform Task Operations (no error is thrown) and SPP recognizes the tasks.

However, they are not documented as supported Platform Tasks in the SafeguardCustomPlatform Wiki Documentation.

REPRO STEPS

  1. Download a sample platform script.
  2. Copy the ChangePassword Platform task. Rename it to ChangeApiKey.
  3. Copy the CheckPAssword Platform task. Rename it to CheckApiKey.
  4. Log into SPP and navigate to Asset Management > Connect and Platforms
  5. Create a new Custom Platform Script and upload the edited script.
  6. Note "Details" tab shows ChangeApiKey and CheckApiKey as Supported Operations.

EXPECTED BEHAVIOR

If API Key operations are truly supported (that is, if underlying logic will actually support their use, and this isn't a false positive in Custom Platform Script function validation), then it would be expected for documentation to be updated to describe supported parameters and proper usage of the Operations. This would be the preferred case.

If they aren't, then it would be expected that the Custom Platform Script validation would fail in SPP.

The same condition may exist for other new(-er) Platform Tasks, though my testing did not verify.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant