> I'm concerned about config updates made through JMX not being persistent > across restarts Reasonably so yeah. I was thinking along the lines of "change to config that is persisted in config file", but now that you mention this I don't think we actually have a precedent for that yet. And the security implications of making durable config changes via a JMX endpoint or vtable mutation are... well, my gut reaction to that is aversion, let's put it that way. :)
Probably better to have the sidecar handle things like that as a control plane endpoint since it's in a good position architecturally to a) modify running node configs on co-located machines, b) persist those config changes to disk (and even (gasp) version them?!), and c) have auth on that. On Thu, Jul 10, 2025, at 8:18 PM, Joel Shepherd wrote: > > > On 7/8/2025 8:22 AM, Abe Ratnofsky wrote: >> +1 (nb) from me as well. Would be nice to have a reference implementation of >> negotiated authentication in the Java driver; I’d happy to collaborate on >> that. > I'd love some help with the driver[s]. I plan to do at least "an" > implementation in the Java driver, but would really appreciate assistance in > refining to the point that it could be considered a reference impl. > > Thanks! -- Joel. >
