Osquery uses basic SQL commands to leverage a relational data-model to describe a device.

osquery

is there any way to force a refresh of the node key?

For a Fleet user I'd recommend deleting the host from Fleet -- that would cause a re-enrollment when the host next checks in and receives a `node_invalid` message.

I imagine there's some equivalent that could be done in any other TLS server implementation.

ah yeah we're not using fleet here (yet) :[

is the node key just `osquery.db/IDENTITY`?

This is relatively easy from the server. Less sure about the client. If you’re re-enrolling, do you need to keep any of the local state? (vs removing the entire database)

&gt; is the node key just osquery.db/IDENTITY?
I think probably not. The node key will be somewhere in the rocksdb database that I would expect to be opaque except when parsed by rocksdb.

<https://osquery.readthedocs.io/en/latest/deployment/remote/#remote-logging>

```{
  "node_invalid": false // Optional, return true to indicate re-enrollment.
}```