XIQ SE and Windows 11 Authentication EAP TLS

[Asifi]

Hello Community,

We have upgraded from Win 10 to Win 11 and are currently using EAP PEAP as the 802.1x authentication method.  I was told this would no longer work with Win 11 and we would need to implement EAP TLS.  I understand EAP TLS is not available for the version of XIQ SE we have - 23.4.12.3.

However, I believe later version of XIQ SE support EAP TLS.  If this is not the case please let me know. Could anyone let me know which minimum version of XIQ SE supports EAP TLS for XIQ SE and will I need a root certificate to be installed on XIQ SE and the NAC devices?

Is there a guide or similar I could use to Implement EAP TLS?

Currently, we use the built in 802.1x authentication via a LDAP server.  This I believe supports MsCHAP, PEAP and EAP-MsCHAPV2 only.

Many Thanks,

[Zdeněk_Pala]

Hi,

not sure what you mean by test AAA, but you can try use Configuration Evaluation Tool. However Configuration Evaluation tool will not check the certificate validity and what certificate will be used. but you can see if changes you done will affect existing end-systems or not.

Good luck!

[Robert_Haynes]

AAA only gives high-level protocol-based filtering. It would be in the Rules -> Auth Type where you could restrict a rule to EAP-TLS for example.

All XMC / Site Engine releases going back years support EAP-TLS.

FTR, you are on 23.04 which is now outside the 12-month support window. Please plan on performing an upgrade of Site Engine / Control to a supported release; minimum is 24.02.15.05 at this time.

[Asifi]

@Robert_Haynes  - thanks for the update.  I will upgrade to the later version.  Can I edit an exist rule and choose EAP-TLS after installing the root certificate on the NAC's?

Thanks,

Thanks,

[Asifi]

Thanks everyone - lots to ponder and think about.

My last question - we have a wildcard certificate already in use and verified by a CA.  Can we use this as the device cert on the NAC's as this already chains back to out PKI root without having to raise a new CSR and getting this verified by a CA.

Many thanks everyone.

[Robert_Haynes]

We do not permit / advise the use of a wildcard certificate for the RADIUS server certificate for backwards compatibility with clients and 802.1x supplicant configurations that simply do not support it.

A RADIUS server cert w/ multiple SANs (FQDNs) is recommended.

Wildcard certificate is compatible with Captive Portal/Web use purposes.