sAMAccount issues

[james.king14]

When user log into VPN, ASA is looking at CAC common Name instead of LDAP sAMAccountName for authentication.   Causing errors within log in script.  User cannot log into the VPN because of the issue. This is a two part problem;  having a certification chaining issue, but LDAP seems to looking for common name instead of looking for LDAP name  on AD

[Philip D'Ath · Accepted solution]

In your LDAP server definition, try using something like:

aaa-server <server> (inside) host a.b.c.d

 ldap-naming-attribute sAMAccountName

Failing that you'll probably need to use an attribute map.

http://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/91831-mappingsvctovpn.html