cisco asa 5520 AD authentication

Using the ASA 5520 to successfully authentication users who are located in an OU below 'Site-B'.
These users are also members of 'Site-B-VPN-ACCESS' group membership.
This works just fine.

Have users in an OU higher in the AD tree (a different location 'Site-A') but who are members of 'Site-B-VPN-ACCESS' group. These users are not able to authenticate.

I'm not the network guy, I'm the AD guy trying to help the network guy.
I'm thinking that the 5520 is looking in the 'SITE-B-VPN-ACCESS' group and after finding the user then checks 'Site-B' and below for the user to verify the account. If a valid user can be found below 'Site-B' all is good and if the user is in 'Site-A' then the 5520 isn't finding the user and fails.

If that is the issue, what command/attribute do I use to configure the ASA to check the entire AD for a user?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

It sounds like maybe you are using LDAP to authenticate. I founds RADIUS to be much simpler to use. I control who has access through group membership changes, and it isn't dependent upon the OU structure. I am also able to easily assign different Cisco group policies with using RADIUS (NPS) instead of LDAP.
You need to make sure the LDAP Attribute Maps are setup correctly.

If you use ASDM, you can go to
AAA/Local Users > LDAP Attribute Map and edit the appropriate Map and go to Mapping of Attribute Value to point to AD OU you are interested in.

It does require knowledge of ASA, but it is actually easy to setup if you realize that you are "mapping" groups in ASA to "groups" in AD.

Also, check under Network (Client) Access > Dynamic Access Policies and edit the proper group name to make sure users with correct attributes are allowed to login.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
WaywardS0nAuthor Commented:

I'll get up with the network folks this morning.
Thanks for the assistance.
I'll report back shortly
WaywardS0nAuthor Commented:
It will be a few days before we get back onto this issue.
I am closing the question and giving credit as I believe thats the issue we'll find.
Thanks again!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.