How to setup 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

PAM Self-Hosted Articles
2 min read
L7 Applicator
No ratings

Question

For most environments, RSA embeds the RADIUS server into the RSA Authentication Identity Manager.
What happens when we configure this for MFA, is the RADIUS server does not support Challenge-Response.
When customers have implemented RSA and LDAP with CyberArk, they use another RADIUS server that is NOT embedded in RSA's Authentication Manager. An example to use CISCO ACS as this accepts Challenge-Response.  Then the user can use LDAP+RSA as the MFA to CyberArk.

RSA Web Agent is not an alternative to solve the RSA MFA challenge as it does not tie the authentication from the RSA Web Agent to the PVWA authentication.  So, in theory, User1 could login to the the RSA Web Agent and User2 could login to the PVWA as they are mutually exclusive.

Answer

If the customer has a working Radius environment, this can be leveraged to provide 2 factor authentication. 
 

This configuration needs to be done via RADIUS authentication only. RADIUS authentication allows for challenge-response.
The only way to configure this is to integrate the Vault with the customer's RADIUS server and have them (the customer) configure their Radius server to expect an LDAP password as the first level of authentication (provided in the PVWA RADIUS auth login page).
Then, have it confirm against LDAP that the username and password is correct, then send a CHALLENGE message back to ask for “PIN+TOKEN”. The PVWA will prompt the user for the challenge message and ask them to enter that information in and click submit again; the Radius server would then need to be configured to process that challenge through their two-factor system.
 

This is the only way this is possible, if they don’t have this multi-factor auth process configured on their RADIUS server, then it cannot be done with our product. They should work with their vendor support to see how they can configure LDAP authentication + a challenge for PIN+Token.

Once they have that, it’s transparent to us.

This has been successfully demonstrated in the wild, but the configuration is entirely up to the customer.

We configure Radius so that the Vault can pass the info on to the Radius server securely

Rate this article:
  • 3501 Views
  • 0 comments
  • 0 Likes
Article Dashboard
Version history
Last Updated:
‎12-15-2021 03:53 AM
Updated by: