Forum Discussion
AlexDC_262478
Nimbostratus
NimbostratusClient Certificate Authentication - Machine or Client cert APM method
Hello,
I understand the Machine cert checker is a client-side check and the client cert checks are performed as part of SSL negotiation. What I'm not sure about is which method to use to do basi...
Hello,
Machine cert auth is heavy for the endpoint. The browser need admin rights to access and present the certificate located within the local machine store. That's why you need to install an helper from F5 on client devices. I think that it works with Microsoft devices only. My rules are if you need a 802.1x like solution so machine cert validation is the right solution. Otherwise, I would recommend to go with client cert auth that offer more flexibility and can be used outside APM. In both case Crl and ocsp checking works the same.
Yann_Desmarest
Cirrus
CirrusHello,
Machine cert auth is heavy for the endpoint. The browser need admin rights to access and present the certificate located within the local machine store. That's why you need to install an helper from F5 on client devices. I think that it works with Microsoft devices only. My rules are if you need a 802.1x like solution so machine cert validation is the right solution. Otherwise, I would recommend to go with client cert auth that offer more flexibility and can be used outside APM. In both case Crl and ocsp checking works the same.
Yann_DesmarestCirrus
CirrusMachine certificate is in the MY within the Local computer store and require admin rights to get access. A user certificate is in the MY of the Personal store of the user connected. Your machine certificate should identify the device against network access like NAC, Wifi access, vpn access, etc.
The question is do you want to identify the device itself or the user that try to connect to your service ?
Mobile/Tablet devices do not have separated store for the device and the user and most of the time you use user certificates for that purpose.
As far as I remember, CRL checking for machine certs works since v12 and we implemented a workaround on older versions