NAC EAP-TLS + Microsoft PKI - custom subject/common name not possible

  • 0
  • 1
  • Question
  • Updated 3 months ago
  • Answered
We have a working setup with Netsight/NAC + Microsoft Windows PKI 2012 R2
Our Clients get Certificates with Auto Enrollment, which they use to authenticate in the network.
Additionally we use LDAP User Groups to put the Clients into different Networks -> UserVLAN, AdminVLAN, InternetVLAN etc.
This works great, but we noticed a problem.
When using a non Windows Device it is possible to set a different Username/Identity that is sent to the Authentication Server.
This can be used to get into a different network than supposed to, if the Username/Identy is valid (eg. Admin)





In another area we used RADIUS User Group to seperate those client families, but this is not possible here because in the certificate from User and Admin there is nothing different than the hostname.

We thought of writing something in the Subject/common name of the Certificate/Template in the PKI. But we don't know how this can be achieved since there is no possibility to write CUSTOM Information.



Any MCSE knows how to deal with that? ;-)
Photo of Anton Sax

Anton Sax

  • 1,242 Points 1k badge 2x thumb

Posted 3 months ago

  • 0
  • 1
Photo of Brian Holmes

Brian Holmes

  • 328 Points 250 badge 2x thumb
why not check the CN on the certificate to see if it matches the username on the request?
Photo of Anton Sax

Anton Sax

  • 1,242 Points 1k badge 2x thumb
sounds good, how is that done?
Photo of Brian Holmes

Brian Holmes

  • 328 Points 250 badge 2x thumb
I am not familure with Netsight, but on Identity Engines this could be written as part of the Authorization rule I believe.
Photo of SH

SH

  • 4,816 Points 4k badge 2x thumb
(Edited)
Photo of SH

SH

  • 4,816 Points 4k badge 2x thumb
Photo of Anton Sax

Anton Sax

  • 1,242 Points 1k badge 2x thumb
hy stephan, 

i know that article. we also used TLS-fields in RADIUS User Groups for other devices/areas
but in that case there is no TLS-field we can use, because the certificates are mostly the same.
except hostname/dns name, but i cannot build a rule from that

for example hostname1 is ADMIN hostname2 is USER

i thought to write in the subject of ther certificate hostname1-ADMIN so I can make a RADIUS User Group *-Admin
Photo of SH

SH

  • 4,816 Points 4k badge 2x thumb
Hello Anton,

if you can write differen SANs (subject alt name) in the certificate you can use this as criteria.
If you can't do this with your certificate template on the Windows CA you can create a new template  (enterprise server needed!) with SAN as attribute.

If this is not possible. You export the serial from Windows CA and import again in the NAC I think.
But therefore you have to dig deeper into the Windows Certificate command line.
Photo of Keene, Scott

Keene, Scott, Employee NMS/GTAC

  • 1,542 Points 1k badge 2x thumb
Hello,

If I am reading this correct, you can use an Appliance Property pushed out to the NAC appliance to ensure that the username matches the Common Name.   This came up once in a troubleshoot so we created a knowledge-base article for it:

https://gtacknowledge.extremenetworks.com/articles/How_To/Configure-NAC-To-Use-The-TLS-Client-Certif...

Does this help?



Regards,

Scott Keene
NMS/NAC Support, Extreme GTAC
Photo of SH

SH

  • 4,816 Points 4k badge 2x thumb
Hello Scott,

I posted that link one hour ago ;-).

Best regards
Stephan
Photo of Keene, Scott

Keene, Scott, Employee NMS/GTAC

  • 1,542 Points 1k badge 2x thumb
Very good, thank you.  I only had time to read the initial inquiry and I remember writing the article so I just replied real quick.  Take care.  -Scott
Photo of Anton Sax

Anton Sax

  • 1,242 Points 1k badge 2x thumb
Thank you for your replies
The radius property seems to do exactly what we want.
I cannot test it at the moment as our certificates don't have a subject/common name so the username cannot be replaced
when the clients have the new certificate we gonna test it