cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
906
Views
0
Helpful
15
Replies

ISE failing user check using TEAP

Chris S
Level 1
Level 1

We have successfully deployed the TEAP policy using Cisco's documentation .   The challenge seems to be that the Machine Compliant policy is the only hit we are getting.  Never hits the Fully Compliant policy.

  • Windows supplicant is provisioned as per documentation to use EAP-TLS for both primary and  secondary EAP methods.  
  • Both computer and user root cert providers are the same
  • User certificate is provisioned for "Client Authentication" and located in the Personal->Cert store on the workstation

ChrisS_0-1706275696752.png

 

We are seeing this in the log - any ideas on what to look for?

 

11627Starting EAP chaining
 11573Selected identity type 'User'
 11564TEAP inner method started
 11521Prepared EAP-Request/Identity for inner EAP method
 11596Prepared EAP-Request with another TEAP challenge
 11006Returned RADIUS Access-Challenge
 11001Received RADIUS Access-Request
 11018RADIUS is re-using an existing session
 11595Extracted EAP-Response containing TEAP challenge-response
 11567Identity type provided by client is equal to requested
 11522Extracted EAP-Response/Identity for inner EAP method
 11806Prepared EAP-Request for inner method proposing EAP-MSCHAP with challenge
 11596Prepared EAP-Request with another TEAP challenge
 11006Returned RADIUS Access-Challenge
 11001Received RADIUS Access-Request
 11018RADIUS is re-using an existing session
 11595Extracted EAP-Response containing TEAP challenge-response
 11515Supplicant declined inner EAP method selected by Authentication Policy but did not proposed another one; inner EAP negotiation failed
 11520Prepared EAP-Failure for inner EAP method
 11566TEAP inner method finished with failure
 22028Authentication failed and the advanced options are ignored
15 Replies 15

Yes, but if the cert has multiple, and maybe the one that ISE picks doesn't match the identity on the AD. To avoid this, you can select the right attribute manually in the certificate authentication profile and see if that fixes the issue.