I'm having problems configuring VPN clients authentication against an LDAP server. The main problem is when the ASA has to decide a group-policy for the non-compliance users.
I use LDAP attribute-maps in the ASA to map the memberOf parameter to the Cisco Group-policy attribute, then I associate memberOf with the AD group that the user must belong to has VPN access and the rigth group-policy. This works correctly.
But the problem is when the remote user isn't in the correct AD group, I set a default-policy-group with no access to this kind of users. After that, all the users (allowed and not allowed) fall in the same default-group-policy with no VPN access.
There is the ASA configuration:
ldap attribute-map LDAP
map-name memberOf Group-Policy
map-value memberOf "cn=ASA_VPN,ou=ASA_VPN,ou=My Group,dc=xxx,dc=com" RemoteAccess
aaa-server LDAP protocol ldap
aaa-server LDAP (inside) host 10.0.0.3
ldap-base-dn ou="My Group", dc=xxx, dc=com
ldap-login-dn cn=user, ou="My Group", dc=xxx, dc=com
group-policy NOACCESS internal
group-policy NOACCESS attributes
group-policy RemoteAccess internal
group-policy RemoteAccess attributes
dns-server value 10.0.0.3
default-domain value xxx.com
tunnel-group RemoteAccess type remote-access
tunnel-group RemoteAccess general-attributes
tunnel-group RemoteAccess ipsec-attributes
As you can see, I have followed all the examples availables in the web to solve the problem but I can't obtain a good result.
Somebody has an solution for this problem????
Solved! Go to Solution.
this should definitely work, i.e. the deny part is already working ok and the user that has the correct memberOf attribute should definitely get mapped to the Allow-Access policy and so should be allowed in.
I'm thinking of this being a bug as well, but I had a quick look and did not see anything matching, and if this were a bug in 8.2.3. then I would not expect you to be the first customer to experience this, so I'm still more inclined to think it is something in the config that we are overlooking (I know frome experience typo's can sometimes be extremely hard to spot).
Could you get "debug aaa common 255" as well please, maybe that will tell us something.
BTW, just to be sure: you did not configure anything (like vpn-simultaneous-logins) in the DfltGrpPolicy, did you? Just double checking since your Allow-Access policy would then inherit that.
Maybe as another test, explicitly configure a non-zero value for that parameter in the Allow-Access policy, i.e.
group-policy Allow-Access attrib
Hi Herbert, thanks for your answer.
I saw the output of the "debug ldap 255" command previously and it was the base to make the config that I've pasted in my previous post.
My problem is when an attribute isn't present in the parameters that the LDAP server pass back to the ASA when authenticate a user, how can I represent these in the ldap attribute-map?
I didn't find documents that explain or shows a configuration to represent values that aren't present in the LDAP attributes pass to the NAS (an ASA in this case).
I map the group with privileges to remote access to the memberOf attribute in an LDAP attribute-map. All the rest of the groups must be not allowed to access but I doesn't want to make this association for each case in the LDAP attribute-map. There is a way to map a generic attribute with wildrcards for example?
I hope that I was clear now with my problem and someone can help me.