Validate the server's identity by validating the certificate with the 'pfSense internalRootCA' certificate selected Use a certificate on this computer - Use simple certificate selection Authentication Type - Smart Card or other certificate Created a manual wireless network profile Windows 10 Wireless network configuration I believe Apple IOS devices may do this slightly differently and supply certificates in a user context which may require further configuration, but for now I'mįocussing on Windows 10 device/machine authentication.ĩ. I want to do device/machine based EAP-TLS authentication therefore with no 'user' involvement. 'The Subject Alternative Name (SubjectAltName) extension in the certificate contains the user principal name (UPN) of the user'. The only requirement I was unsure of was: I have checked the Microsoft 'Certificate requirements when you use EAP-TLS or PEAP with EAP-TLS' document and believe the configuration and details in the certificates meet these requirements. Exported the Windows 10 Desktop Client and imported into the 'Certificates - Local Computer - Personal Store' no certificate trust errors in the web browser when accessing the web interface.Ĩ. I also created a certificate from this CA for the pfSense web interface using this root CA and tested that the Windows 10 client is successfully trusting the root CA certificate i.e. Exported the CA root certificate and imported into 'Trusted Root CA store' on the Windows 10 Client. Configured Cisco Enterprise wireless access point to use the freeradius server with shared secret and created a SSID with WPA2 Enterprise.ħ. SSL Server Certificate - certificate selectedĦ. SSL Revocation List - internalRootCA Revocation List selected Most settings left default (Type - Authentication, Port 1812 etc) Created a new interface for the Cisco Enterprise Wireless Access point to use Added a entry for the Cisco Enterprise Wireless Access point Created a new certificate for the Windows 10 Professional Client (I went with this naming convention to support a future move to an internal domain - was this an incorrect decision ? I've replaced the real domain name with domain.local for the purpose of this internet post)Ĥ. Existing pfSense router - Added FreeRadius3 packageģ. Windows 10 Professional client (standalone not domain)ġ. I have summarisedīelow the steps I have followed, important bits of configuration and importantly windows event log error entry: I'd really appreciate any advice on where I am going wrong which I think is most likely certificate related. I believe I have implemented the configurationĬorrectly using a range of documentation and guides, but my initial testing with a standalone Windows 10 client is not going well. I am trying to use pfSense to support EAP-TLS with WPA2-Enterprise (machine/device authentication, not user authentication) for wireless clients using FreeRADIUS and pfsense CA on my existing working pfSense server.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |