Last Modified: Jun 02, 2022
See more info
Known Affected Versions:
14.1.0, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 14.1.2, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 14.1.3, 18.104.22.168, 14.1.4, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 14.1.5
Opened: Dec 09, 2021
When an admin adds a member to a pool that is used in an LDAP AAA object, the changes are not synced properly with Policy Sync. With the Location Specific property enabled, Policy Sync creates a node on the destination device is an error. With the Location Specific property disabled, Policy Sync creates a node on the destination device, but does not create a pool member in the AAA pool.
Changes to LDAP AAA objects are not synced as expected with Policy Sync.
-- LDAP AAA object present in Access Policy -- Access Policy synced with Policy Sync
Manually update the AAA pool on the destination device as required.