ā05-07-2024 05:13 AM
Our remote workers utilize RAVPN by installing AnyConnect software on their work machines. To distinguish users based on their groups, I employ Group Policy. While the authentication process is functioning correctly, an issue arises where any authorized user can access VPN profiles belonging to other groups. We have configured AD on the authentication server.
How can I configure the AD and FMC to ensure that users are authenticated solely based on their respective groups, thereby isolating them from accessing VPN profiles outside of their designated groups?
Solved! Go to Solution.
ā05-07-2024 07:20 AM
You can assign group-policy with LDAP attribute maps when users are authenticated to AD via LDAP. For this you can use memberOf LDAP attribute or some other attribute in LDAP schema:
memberOf attribute is ok if a user belongs to a single AD group for mapping purposes, otherwise the mapping can lead to unexpected results.
ā05-07-2024 07:20 AM
You can assign group-policy with LDAP attribute maps when users are authenticated to AD via LDAP. For this you can use memberOf LDAP attribute or some other attribute in LDAP schema:
memberOf attribute is ok if a user belongs to a single AD group for mapping purposes, otherwise the mapping can lead to unexpected results.
ā05-09-2024 03:21 AM
Thank you, it was effective for me based on the URL. I work for the LDAP attribute maps on the Authorization, and it worked.
ā05-07-2024 08:47 AM
ā05-08-2024 12:56 AM
DAP is unnecessary to achieve this goal.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide