We've been rolling out JumpCloud RADIUS for our corporate WiFi, and while the success rate is high, the failures were a black box. Trying to correlate a user complaint with the JC admin logs was a manual, time-consuming process.
I built a simple internal dashboard to visualize these failures in near real-time. It pulls from the JumpCloud Events API (specifically the `radius_auth` events with a failure outcome). The key was filtering for the `access_reject` reason and mapping it to the specific RADIUS server IP and user.
The main insight so far: a significant portion of our rejects aren't password issues, but users attempting to connect from devices not yet registered in JumpCloud. The dashboard makes this pattern obvious, so we can adjust our onboarding workflow.
This isn't a replacement for proper monitoring, but it's a practical stopgap. If anyone else is wrestling with RADIUS visibility, I can share the general approach. What methods are you all using to track and troubleshoot these kinds of auth flows?
—AF