View Cart
0 Items | Total: US$0.00
Welcome,      Register

You are here

SEC0334 - ISE 3.0 EAP Chaining with Cisco NAM and TEAP (Part 3)

Rating: 
5
Average: 5 (1 vote)
Difficulty Level: 
4
Lab Document: 
<Please login to see the content>
Video Download: 
Title: SEC0334 - Video Download $17.00
Purchase SEC0334 - Video Download $17.00

The video demonstrates a use EAP Chaining on Cisco ISE 3.0. We will step through necessary authentication and authorization policy configuration for wired and wireless. We will go through configuration of NAM Profile Editor for AnyConnect NAM module. Testing will be performed on wired and wireless to show how EAP Chaining appears on ISE authentication log. The video ends with a discussion and configuration of TEAP on Windows Native Supplicant.

Part 3 of this video covers TEAP

Topic:    

  • Policy Element
    • Allowed Protocol
    • Downloadable ACL
    • Authorization Profile
  • Policy Set
    • Authentication Policy
    • Authorization Policy
  • AnyConnect Secure Mobility 4.x (NAM Module) on Windows 10
  • NAM Profile Editor
  • EAP-Chaining with EAP-FAST (MSCHAPv2, TLS)
  • User and Machine Authentication
  • TEAP (Tunneled Extensible Authentication Protocol)

About Author

Metha Chiewanichakorn, CCIE#23585 (Ent. Infra, Sec, SP), is a Cisco networking enthusiast with years of experience in the industry. He is currently working as a consulting engineer for a Cisco partner. As a founder of and an instructor at labminutes.com, Metha enjoys learning and challenges himself with new technologies.

2 comments

Hi. Excellent series, this video is by far the most comprehensive guide for EAP Chaining using TEAP in a Windows environment. We are testing this now in a k12 environment using TEAP on Windows 11 22H2 and ISE 3.0. We are trying to EAP-MSCHAPv2 for primary and secondary EAP method for authentication. However we are seeing the "Automatically use Windows logon name and password (and domain if any)" check box greyed out for both settings. Credential Guard is disabled and we have attempted most if not all of the documented fixes we can find. Have you tried deploying TEAP on Windows 11 on your lab and do you have any suggestions? Thank you.

We have not tested but on a Win11 computer, we can see the "Automaically use Windows login name" option selectable. Could that be specific to domain computer and your GPO settings? Do you have the same problem on a non-domain computer?