Forum Discussion
Hi,
Machine certificate check require Admin right on the client side. That's why you should deploy "Machine Certificate Checker" within the Edge Client and install EC with admin rights.
Then, in addition to the Trusted CA, you need to add Common Name or Issuer matching text to the Machine Certificate Check in the VPE.
- Martin_VlaskoAug 10, 2018
Altocumulus
Hi,
I did not mention it, but all that I have done already. The checker is installed together with the EC and the whole thing has been installed with admin rights.
In APM policy machine certificate check action I do have the 'Match subject CN with FQDN' set to YES and even the 'Match Issuer' set to the correct string.
I mean, I am pretty sure I managed to configure everything based on the available documentation. My question here was more the direction... if it does not work for whatever reason, what is the way to find out why is it not working?
I cannot imagine there is no way to somewhere see the real actual reason of the error, it must be written somewhere.. I just don't know where, couldn't find it yet.
Looks like I will have to open a ticket with F5 support.
- Yann_Desmarest_Aug 10, 2018
Nacreous
Hi,
You can check the log file on the client itself. It will help you to understand the problem.
You can also download F5 CTU (Client Troubleshooting Utility) and run it on the client.
https://support.f5.com/csp/article/K12444
- Martin_VlaskoAug 10, 2018
Altocumulus
Hi there,
Log file from the client I checked already, it's in my original post above. Not really helpful the messages in it.
But I can give a try to the CTU, I thought it would produce just the same type of logs as I already have, but I will give it a try and let's see.
thx for the tip.