pspete / psPAS

PowerShell module for CyberArk Privileged Access Security REST API
https://pspas.pspete.dev
MIT License
286 stars 90 forks source link

Set-PASSafe SafeName not being passed #509

Closed MichaelCoey closed 6 months ago

MichaelCoey commented 7 months ago

Describe the issue Upon calling the Set-PASSafe command we are seeing the error: Invoke-PASRestMethod : [400] There are some invalid parameters: Missing mandatory parameter [SafeName].

The issue is that the safe name is not missing and is being placed in the code. All other safe commands are working as expected except this call.

To Reproduce Steps to reproduce the behavior:

  1. Login with valid account with permissions
  2. Attempt to update safe description using Set-PASSafe function
  3. Call will fail due to SafeName error

Expected behavior If completed successfully we expect to see the safe description updated on the target safe

Screenshots & Console Output If applicable, add screenshots and/or console output to help explain your problem.

<--Console Output Goes Here-->



**Your Environment**
Include relevant details about your environment

* psPAS Version: 6.0.30
* CyberArk Version: 13
pspete commented 6 months ago

Hi @MichaelCoey

Without sample code it is hard to comment further. Unfortunately we are unable to replicate the issue using the steps provided. Can you share your (sanitised) output when specifying $DebugPreference = "Continue" so we see the safename being specified in the request body? image

Can you provide additional context, or test the api activity outside of psPAS to confirm if the same issue is observed or not? See: https://pspas.pspete.dev/docs/troubleshooting/#manual-api-command-testing

pspete commented 6 months ago

Any update on this @MichaelCoey - ok if we close the issue?

pspete commented 6 months ago

Closing: no update