I'm setting up a new ASA with VPN access and am trying to decide which authentication method to use LDAP or RADIUS. I was wondering if there were any pros or cons to either way. I'm trying to control access by Active Directory Group.
Not sure about any advantages/disadvantages to either but since you are authenticating against AD it would be simple for you to set up IAS on your domain controller.
From my own opinion, the advantage of using AD as the authentication server is that, passwords can expire after a number of days. Well, it still really depends on the password policy of your domain. That is one of the disadvantage of using Cisco ACS, the password won't expire after few days or months.
I am working with AD and testing out both the IAS RADIUS and the LDAP for SSL VPN, and there are a few differences.
SSL VPN in clientless mode allows for password management, so the end-user can update their pw from the login page.
LDAP allows you to notify the user X number of days before the pw expires and allow them to change it (# of days is configurable; secure LDAP is required, but not hard to set up).
RADIUS, again per the documentation, can only notify the user, and allow them to change the password, when it expires.
I am also trying to configure framed-ip-addresses, so that as users log in via the SSL VPN Client (AnyConnect), they will always get the same IP address. I can get the framed IP to work with RADIUS, but not LDAP.
LDAP also works very nicely with DAP in the SSL VPN, too, which allows you to add functionality to the profile assigned to a user a login based on AD group membership.
These are a few of the differences that I have found, so far.
This seems to be doable, but I have not done it here (I am running SSL VPN and using DAP, which certainly works with AD groups).
It looks like you configure an LDAP attribute map to the IETF-Radius-Class, (and then map your AD groups to ASA groups if the group names do not already match). See page 13-15 and Appendix E in the CLI Config Guide.
I am in the same situation as you. I am currently using IAS on my Windows 2003 DC to authenticate remote users (IPSec VPN tunnel)via the Radius protocol. I was able to sucessfully authenticate users against Active Directory.
Now, the real issue is that we have a lot of remote users and they need to be able to change their Domain Passwords if they expire, or get notifications when their passwords are about to expire.
I was confused on what you posted: " RADIUS, again per the documentation, can only notify the user, and allow them to change the password, when it expires."
When using the RADIUS protocol over an IPSec VPN tunnel, are remote users able to change their passwords? Or only get notified when the password expires ? Thanks in advance.
If you look in the ASDM under your connection profile for your Remote Access users. Look under Advanced there's an option "Enable notification upon password expiration to allow user to change password".
That's the only place I can see to try and make it work.
My ASA is running 7.2(2). If you run across any documentation regarding password managment via Radius, please share. I've come across LDAP Authorization that allows this, but not RADIUS. Thanks.
Password-management will work with Radius and LDAP. When using radius you will not be notified a certain number of days before password expiration, but you will be notified when it expires and will be able to change it.
When my client connects to our PIX then he is prompted for his AD username and password. If the password has expired it just keeps asking him for his password and then locks his account.
What have I do wrong or maybe better how do you properly set this up on a radius server.
This is the command you are looking for.
Once enabled on the firewall all you have to do is make sure you are allowing mschap v2 in your remote access policy on IAS server.
When the user connects to the vpn and their password has expired, it will prompt them to change their password.
hostname(config)# tunnel-group group-name general-attributes
edit: There is also a checkbox in the remote access policy in IAS to "allow user to change password after it expires"...check it.
It sounds like you are using LDAP right now. In order to enable password management with LDAP you must use Secure LDAP. At the command line it is "ladp-over-ssl", in ASDM it is a check box on the LDAP server page. (LDAP configuration starts at page 13-12 in the 8.0 CLI Config Guide; the requirement for LDAP over SSL to enable password management is mentioned on page 30-10).
To enable LDAP over SSL on the AD LDAP server you will need to install a certificate on the server. Once the certificate is installed no other configuration is required on the AD server.
HI I am trying to get my asa to use a radius server and authenticate with the domain, i just cant seem to get it to work. when i do the test in the asa it always fails. i do get an error on the server about wrong password but i still cant figure it out, any direction would be appreciated
Verify the you are using MS-CHAPv2 on your radius server under IAS and Routing and Remote Access services and on your ASA. It would help if you have more details about your configurations. Thanks.
The "test" feature in the ASA uses PAP. If PAP is not enabled on your radius server it will fail with invalid password.
If you are running IAS, enable PAP in the remote access policy or test from a vpn client, not from the "test" function in the ASA.
yep tried it still get user rejected the reason it says in windows is The connection attempt did not match any connection request policy.
but i do have a policy setup.
Try it without the username value. By default the policy "use windows authentication for all users" is only set to day and time restriction permit all. I would try that.