09-22-2015 01:32 AM - edited 03-17-2019 04:22 AM
Hi everyone,
I'm trying to authenticate deskphones (LSC certs, not MIC) via EAP-TLS. I'm using the latest version of Radiator AAA server. I've read on the forum how this is done for phones which authenticate with a MIC, but I'm interested in the more secure LSC solution. My cluster is in mixed mode and each phone has an LSC installed.
As part of the configuration I need to supply the public and private key for the server authentication. I'm assuming the CAPF-trust certificate called CAPF-xxxxxxxx.pem is the public key (I took the one which appears under every phone's security menu). Anyone know how to extract the private key?
Better yet, can anyone provide a snippet of radiator configuration for authenticating with LSC?
Thanks for the help :)
09-22-2015 03:51 AM
Hi,
Did you use self-signed certificate for CAPF or you installed signed one.
09-23-2015 01:48 AM
Created via CTL client and two SASTs to sign it, so it should be self-signed.
If I were to take a SAST and use Safenet utility used for the CTL client, would the exported certificate be the server's private key? Would I need all such certificates from the SASTs for EAP-TLS?
09-24-2015 01:48 AM
Does anyone have any idea how to extract the private keys of the CAPF (which was installed via CTL client)?
09-29-2015 04:10 AM
With some trial and error I've found how to configure Radiator to authenticate by EAP-TLS with LSC certificates. Below is the relevant handler for 78xx series phones:
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide