10-23-2019 11:50 PM
Hi,
I'm using anyconnect NAM as a supplicant in my windows 10 (ver 1903) using wired authentication.
I'm using ISE 2.4 with patch 10 installed with EAP-FAST for the protocol.
I already configured the proper settings for the NAM using the profile editor.
Whenever I authenticate using the nam, I use username@domain.com as my username.
When I view the radius live logs in ISE I get identity not found in identity store and I noticed that under the identity the username only appears without the domain.
I'm using and LDAP server as an external identity in ISE.
Is there someone having the same issues? is there something wrong in the config? or some bug maybe with anyconnect? not sending the actual username.
Solved! Go to Solution.
10-24-2019 09:14 PM
10-25-2019 09:41 AM - edited 10-25-2019 09:43 AM
AFAIK the usernames come from the 802.1X supplicant but not what set by ISE. Thus, please double-check how the username format is set in Configure User Credentials of AnyConnect NAM profile.
If your LDAP has an attribute matching the username format without "@domain.com", then you may pick that as the subject name attribute instead.
If it still an issue, please generate an AnyConnect DART bundle and engage Cisco TAC support.
10-24-2019 12:34 AM
10-24-2019 06:41 PM
10-24-2019 09:14 PM
10-25-2019 09:41 AM - edited 10-25-2019 09:43 AM
AFAIK the usernames come from the 802.1X supplicant but not what set by ISE. Thus, please double-check how the username format is set in Configure User Credentials of AnyConnect NAM profile.
If your LDAP has an attribute matching the username format without "@domain.com", then you may pick that as the subject name attribute instead.
If it still an issue, please generate an AnyConnect DART bundle and engage Cisco TAC support.
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