To start setting up Client VPN (SSL or IPSec) you need the following info:
===============
1) Active Directory Server IP (for LDAP query)
2) Firewall user name and password in AD (for firewall to be able to query LDAP)
3) Output for the "dsquery user -samid <firewall username>" command on your AD server.
4) IP address for VPN pool
5) Output for the "dsquery user -samid <example vpn username>" command (use to set up VPN users)
6) DNS Servers IP addresses
7) What internal networks/resources your VPN clients will be allowed to access?
====================
Set up an AAA server of type LDAP, configure the server using the AD/LDAP info obtained earlier. Create a group-policy, tunnel-policy, and domain user (on AD server) for LDAP to FW binding. Here's a sample using dummy data:
ldap attribute-map LDAP.To.Group.Policy.Map
map-name memberOf IETF-Radius-Class
map-value memberOf CN="VPN Users,OU=company,DC=ad_dom
aaa-server LDAP-SRV-GRP protocol ldap
aaa-server LDAP-SRV-GRP (inside) host 10.12.13.14
ldap-base-dn cn=Users, dc=ad_domain, dc=local
ldap-scope subtree
ldap-naming-attribute sAMAccountName
ldap-login-password abc123
ldap-login-dn cn=authproxy, cn=Users, dc=ad_domain, dc=local
server-type microsoft
ldap-attribute-map LDAP.To.Group.Policy.Map
group-policy No.VPN.Access-GP internal
group-policy No.VPN.Access-GP attributes
vpn-simultaneous-logins 0
group-policy ADVPN_RA attributes
vpn-simultaneous-logins 3
tunnel-group ADVPN_RA general-attributes
authentication-server-grou
default-group-policy No.VPN.Access-GP
tunnel-group ADVPN_RA ipsec-attributes
pre-shared-key ***
Main Topics
Browse All Topics





by: asavenerPosted on 2009-07-27 at 06:05:10ID: 24951063
I don't think there's any need for IAS; the ASA is capable of performing Kerberos authentication.
cisco.com/ en/US/prod ucts/hw/vp ndevc/ps20 30/ product s_configur ation_exam ple09186a0 08060f261. shtml
http://www.