generate access_token using username, password with OTP based login about epv-api-scripts HOT 6 CLOSED

Hey @samiron7567 ,

Try concatenating the OTP password with a comma after the password
an example for it (in Powershell) can be seen here:
https://github.com/cyberark/epv-api-scripts/tree/master/Account%20Onboard%20Utility/v10

and a video tutorial by @infamousjoeg here:
https://www.youtube.com/watch?v=zxzUfEUN5dA&t=647s

from epv-api-scripts.

Is there a simple way of getting this RestAPI worked with application like Postman? I am not a powershell lover and its hard for me to understand from the referred powershell script.

And mostly why CyberArk has such bad documentation. Everywhere they populated document to use authentication other than OTP. They must provide more info on their documentation sites of how one can use various login procedure for automations.

from epv-api-scripts.

@samiron7567 our REST API is documented in a Postman collection at https://CYBR.rocks/RESTAPI.

from epv-api-scripts.

@samiron7567 in addition to the public Postman, there is also a swagger documentation on the PVWA instance that is installed at your organization.
Just go to https:///PasswordVault/Swagger
There you will get the up to date REST API methods for your version

from epv-api-scripts.

Thanks for the reply @AssafMiron however its same as i was following documentation earlier. It is asking for MFA but there is no guide, where to put MFA actually within the document

curl -X POST --header 'Content-Type: application/json' --header 'Accept: application/json' -d '{ \
"UserName": "aabcdzz", \
"Password": "mypass", \
"Type": "string", \
"SecureMode": true \
}' 'https://pam.example.com/PasswordVault/api/Auth/radius/Logon'

Here is output with Response code 500

{
"ErrorCode": "ITATS542I",
"ErrorMessage": "Enter the current code displayed in the Multi-Factor Authentication or Azure Authenticator mobile app to complete your authentication."
}

from epv-api-scripts.

@samiron7567, when returning ITATS542I, a response to the Radius challenge is expected.
This exception can be caught, and a second authentication request sent containing the OTP as the password value.
Here is some tried & tested code which illustrates the logic: https://github.com/pspete/psPAS/blob/3efbf916908b04ddb761140dffa7cc2914d4df5e/psPAS/Functions/Authentication/New-PASSession.ps1#L540

from epv-api-scripts.