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
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
Download a sample platform script.
Copy the ChangePassword Platform task. Rename it to ChangeApiKey.
Copy the CheckPAssword Platform task. Rename it to CheckApiKey.
Log into SPP and navigate to Asset Management > Connect and Platforms
Create a new Custom Platform Script and upload the edited script.
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.
The text was updated successfully, but these errors were encountered:
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
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.
The text was updated successfully, but these errors were encountered: