REST API authentication using RADIUS challenge/response

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

REST API authentication using RADIUS challenge/response

L1 Bithead

How does one authenticate against the REST API when CyberArk is configured for RADIUS authentication with a challenge/response? To login we put the access token in for password and then we are challenged with LDAP password.

 

With this configuration I can't figure out how to authenticate. I need to be able to pass both LDAP password and access token.

5 REPLIES 5

L1 Bithead

Perhaps this was already covered here:

https://community.cyberark.com/s/question/0D55000006JFJr0CAH/in-an-environment-with-radiusmfa-enabled-what-is-the-best-way-for-teams-to-programmaticallynoninteractively-access-the-rest-apis

 

Looks like it can't be done. All you can do is configure separate accounts for API access using a different form of authentication.

L4 Transporter

@Travis Golliher​ You can use the following body in your authentication call to get the token

 

{

"username":"abcxxxx",

"password":"xxxxxx",

"useRadiusAuthentication":YES

}

 

in the "password" section you need to put the token code (I've tested and it works). But again, since it doesn't ask for your windows/LDAP i'm doubtful if its 2FA

L4 Transporter

I've saw a couple of similar posts regarding this and I just dont get it.

Why would you enable 2FA on a feature designed for programing and non-interactive sessions?

​

2FA is there to protect people, not service accounts..

L5 Sessionator

does the latest video from @Joe Garcia​ help?:

https://cybr.rocks/duo-2fa

 

 

Doing things non-interactive doesn't inherently make it more secure. If you grant privileges to these service accounts and they are only single factor auth how do you protect them?  I can see possibly a solution with a credential provider maybe.

 

One interim workaround I was thinking about is making a read-only service account (no access to creds as well) so that I can at least audit/report with the REST API.

  • 1305 Views
  • 5 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!