Cisco Bug: CSCvi07018 - ENH Let FMC to change ldap-naming-attribute from GUI
Mar 04, 2019
- Cisco Firepower Management Center
Known Affected Releases
Symptom: User after creating the RA VPN policy can only login to the Anyconnect profile by using the samaccountname naming attribute and in ASA he was able to use userPrincipalName to login. By default FMC pushes the attribute like below: - For realm type AD: aaa-server Test_AD host X.X.X.X ldap-naming-attribute samaccountname - For Realm type LDAP: aaa-server Test_AD host X.X.X.X ldap-naming-attribute uid It should be possible to configure with FMC GUI custom attribute, e.g.: aaa-server Test_AD host X.X.X.X ldap-naming-attribute userPrincipalName Conditions: RA VPN User authenticated agains AD/LDAP.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases