01-13-2025 09:40 AM
Currently on a Cisco ASA, we use RADIUS authentication for WEBVPN users. For the logs on the RADIUS server we are not receiving the originating public IP of the users failed/successful attempts, rather we are getting OUR public IP of the gateway for WEBVPN. The RADIUS server is setup use attribute 31 for the source.
To attempt to find the correct attribute I did a "debug radius all" but only received the binary values for the attributes therefore not telling me the correct attribute that is giving the source.
I do know that Cisco has vendor specific attributes that gives a string with the source IP, but I am unsure if the RADIUS server can parse through this to just use the source IP. Please let me know if any experience or ideas to try.
01-13-2025 09:52 AM
Check the Asa radius support attribute
MHM
01-13-2025 01:49 PM
Why use RADIUS at all? What is the MFA strategy here? Why not use a SAML Flow instead?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide