Hello Team,
We are facing an issue with PSPAS PowerShell execution using CyberArk REST API Radius authentication and would appreciate your assistance.
A few weeks ago, we were successfully able to execute PSPAS PowerShell scripts using CyberArk REST API Radius authentication without any issues. However, currently we are encountering problems during authentication.
When we test the REST API Radius authentication directly through Postman, we initially receive a 500 Internal Server Error response along with a message requesting a verification code. After that, when we send another API request including the username and OTP/verification code, we are able to successfully obtain the authentication token.
However, when attempting the same flow using PSPAS PowerShell, the process is not successful. Specifically:
- Initial authentication attempt results in a 500 Internal Server Error
- During the second attempt (when providing the OTP/verification code), we receive either 500 Internal Server Error or 403 Forbidden
- As a result, the token is not being generated through PowerShell
Since this workflow was functioning correctly previously, we would like your guidance on whether there have been any changes related to PSPAS handling of Radius authentication, OTP flow, or API behavior.
Please let us know if additional logs, screenshots, request details, or debugging information are required.
Thank you for your support.
Regards,
Mukesh Solanki
Hello Team,
We are facing an issue with PSPAS PowerShell execution using CyberArk REST API Radius authentication and would appreciate your assistance.
A few weeks ago, we were successfully able to execute PSPAS PowerShell scripts using CyberArk REST API Radius authentication without any issues. However, currently we are encountering problems during authentication.
When we test the REST API Radius authentication directly through Postman, we initially receive a 500 Internal Server Error response along with a message requesting a verification code. After that, when we send another API request including the username and OTP/verification code, we are able to successfully obtain the authentication token.
However, when attempting the same flow using PSPAS PowerShell, the process is not successful. Specifically:
Since this workflow was functioning correctly previously, we would like your guidance on whether there have been any changes related to PSPAS handling of Radius authentication, OTP flow, or API behavior.
Please let us know if additional logs, screenshots, request details, or debugging information are required.
Thank you for your support.
Regards,
Mukesh Solanki