cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1434
Views
5
Helpful
9
Replies

Match EAP-TLS as Authentication Condition

victguti
Beginner
Beginner

Hello,

 

I am trying to create an authentication rule to match EAP-TLS authentication requests but the system (ISE 2.2 Patch 7) doesn't allow me. As you can see on the attached screenshots, I receive a warning when I create the Authentication Compound Condition and I am not able to use it in the Authentication policy.
If I add the condition manually (Add/Attribute Value) on the authentication rule, I don't receive any warning (also screenshot attached).

 

I would like to know:
- Why I cannot use a Library Compound Condition but I can add the condition using Add/Attribute Value in the authentication rule?
- If I do it using Add/Attribute Value in the authentication rule, will this configuration work?

 

Thanks and regards,

Víctor.

1 Accepted Solution

Accepted Solutions

howon
Cisco Employee
Cisco Employee

Victor, looks to be ISE UI bug. If you can use it as manually (Or AKA 'in-line') condition within the authentication rule then it is certainly supported.

By the way, if it is just one condition, you could try it with simple condition instead of compound condition if you still want to use library instead of in-line.

View solution in original post

9 Replies 9

paul
Advocate
Advocate

Why do you want to call out EAP-TLS specifically in the authentication phase?  Just build an Identity Source Sequence that encompasses both your Active Directory domain and your Certificate Authentication Profile (CAP) and you can cover both PEAP and EAP-TLS use cases in your authentication phase.  Use the default authentication rule and assign the ISS.  The only reason to call out specifics in the authentication phase is if you have different CAPs.  With modern certs using SAN fields for almost everything you rarely if ever need a CAP other than pointing at the SAN field for identity information.

Hi Paul,

 

Many thanks for your answer. Using an ISS was also my first approach but it is a requirement of the project to split each authentication protocol in an authentication rule.

As per ISE configuration we should be able to do it as it is allowed to use these attributes as condition in a authentication rule. However, it is quite strange that if we create a Compound Condition with the same condition, it cannot be used in the authentication rule (I know it can be used in a sub-rule but it doesn't fit the case I want to cover). That's why I am wondering if it is a supported configuration that will actually work or it shouldn't be allowed by ISE interface to use EAPAuthentication or EAPTunnel attributes in the first condition of an authentication rule.

 

Regards.

I can't remember what condition works in that version of code to split it out at authentication phase.  In 2.3+ you can use Network Access:EAP Authentication like you are trying to use.  

 

Honestly, the requirement makes no sense.  Part of our job as ISE installers is to educate the customer on how ISE works and steer them to the correct setup.  Saying they want to split out EAP-TLS/PEAP in the authentication phase means they don't understand how the ISS works and are making the authentication configuration more complex and less efficient with no security benefit.  You will still need to do protocol checks in the authorization phase if you are going to allow more than EAP-TLS.

 

The basic fundamental of ISE that I emphasis with all my customers is the authentication phase only job is to answer the question "Are the credentials provided correct?".  Any AD account (and local accounts of if you allow them) and any valid certificate from CAs you trust for client authentication should pass the authentication phase.  All the magic of ISE happens in the authorization phase.

howon
Cisco Employee
Cisco Employee

Victor, looks to be ISE UI bug. If you can use it as manually (Or AKA 'in-line') condition within the authentication rule then it is certainly supported.

By the way, if it is just one condition, you could try it with simple condition instead of compound condition if you still want to use library instead of in-line.

Many thanks howon!

imihajlo
Cisco Employee
Cisco Employee

Hello Hosuk,

This authentication rule has been configured but it never get matched - even when it should.

 

Once again please – is this really supposed to work? Is this supported by design?

 

Many Thanks

I have validated the following setup works with both 2.4p3 and 2.2p10. The setup is a bit convoluted with 2.2 since you have to make a rule with dummy condition that will be true all the time (called ‘Auth1’ in my example below).

ISE 2.4p3:
Screen Shot 2018-09-20 at 1.40.46 PM.png

ISE 2.2p10:

Screen Shot 2018-09-20 at 1.40.24 PM.png

 

Hi, 

I am trying to build a policy that can differnciate between EAP-TLS and PEAP as we migrate from one to another. I am trying to achieve this by configuring and authentication policy that matches based on the same configuration as victguti has in his second image. ( if NetworkAccess>EapAuthentication>Equals>EAP-TLS). However, under network access, EAPAuthentication does not appear as an option and if I create a condition manually to match it, it appears in the list but is greyed out and cant be selected. Any Ideas at all? 

 

Many Thanks

 

You don't need to break it out in the authentication section. That is why ISE has identity source sequences. . Our standard setup is:



1) Create a certificate authentication profile (CAP) to specify where in the certificate you want ISE to collect the identity from, usually the SAN field.

2) Create an identity source sequence, we usually call it Cert_Active_Directory, that ties together the CAP and your AD source.

3) Apply the identity source sequence to the default authentication rule in your policy set.



Then all your work happens in the authorization phase. You specify PEAP or EAP-TLS in your authorization rules to match the different conditions you want to allow.


Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: