![]() ![]() Not only does the common name have to match but the public certificate being served by FleetDM and the local certificate saved on the endpoint must match as well. Below I have included a screen to demonstrate what I mean. When the Osquery agent connects to FleetDM it will verify that the common name in the public certificate being served by FleetDM matches the common name specified in the osquery.flags file: -tls_hostname=. This blog post will assume you have the knowledge and capability to create a DNS A record that points to where FleetDM is being hosted. ![]() Important note : Common name match for Osquery cert check It’s especially useful for talking to multiple devices at the same time. Deploying osquery with Fleet enables programmable live queries, streaming logs, and effective management of osquery across 50,000+ servers, containers, and laptops.
0 Comments
Leave a Reply. |