Hello @TheBroach ,
Most definitely - there is intended to be an “enhanced auth” section within the documentation that looks to be not properly linking at this time - I’m coordinating with our team to investigate that presently.
As for the configuration here, it looks like we may have missed a step during the JKS import process, and instead of using the imported keystore are using the pem file directly. This document outlines the process for creating the client keystore from the pem file. Please bear in mind that some information, like the broker configuration steps, or the initial creation of the pem file, may not be accurate for your use-case, as this is specific to the HiveMQ Broker. That said, the details outlining the client process is accurate, and should walk you through the process. This can be found here.
Best,
Aaron from HiveMQ Team