https://community.cisco.com/t5/network-access-control/ise-using-outer-identity-vs-inner/m-p/3880986#M471907 <P>Disregard, this was determined to be a supplicant side issue.&nbsp;</P> Thu, 27 Jun 2019 18:12:00 GMT jthullen 2019-06-27T18:12:00Z https://community.cisco.com/t5/network-access-control/ise-using-outer-identity-vs-inner/m-p/3880803#M471904 <P>We have recently started to test using the MS WIndow's native supplicant vs NAM. The native is setup to use PEAP (MS-CHAPv2) for both machine and user. Its also setup to protect the real ID by using Anonymous as the outer. This is exactly how we do it when using NAM, save for when using NAM we run EAP-FAST. ISE process the Inner when using NAM and EAP-FAST, but when using Native and PEAP, all auths are showing up, and failing, as user name Anonymous. Is there a setting in ISE we are missing to have it parse the inner vs outer of identity?&nbsp; Please advise and thank you in advance for your help!&nbsp;</P> Thu, 27 Jun 2019 14:01:22 GMT https://community.cisco.com/t5/network-access-control/ise-using-outer-identity-vs-inner/m-p/3880803#M471904 jthullen 2019-06-27T14:01:22Z https://community.cisco.com/t5/network-access-control/ise-using-outer-identity-vs-inner/m-p/3880986#M471907 <P>Disregard, this was determined to be a supplicant side issue.&nbsp;</P> Thu, 27 Jun 2019 18:12:00 GMT https://community.cisco.com/t5/network-access-control/ise-using-outer-identity-vs-inner/m-p/3880986#M471907 jthullen 2019-06-27T18:12:00Z